Triple
T7601098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Propædia |
E179984
|
entity |
| Predicate | introducedInEdition |
P29731
|
FINISHED |
| Object | 15th edition of Encyclopaedia Britannica |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 15th edition of Encyclopaedia Britannica | Statement: [Propædia, introducedInEdition, 15th edition of Encyclopaedia Britannica]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedInEdition Context triple: [Propædia, introducedInEdition, 15th edition of Encyclopaedia Britannica]
-
A.
introducedInProduct
chosen
Indicates that something (such as a feature, component, or concept) first appeared or was initially made available within a particular product.
-
B.
introducedFrom
Indicates that one entity was brought, originated, or caused to appear in a context, system, or environment by another entity.
-
C.
introducedFor
Indicates that one entity was presented or brought to the attention of another entity for a specific purpose or role.
-
D.
introducedInSystem
Indicates that an entity was first added, implemented, or made available within a particular system.
-
E.
introducedInYear
Indicates the year in which something was first introduced, launched, or made available.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69c69f3567008190ab01d2ca7b53584a |
completed | March 27, 2026, 3:16 p.m. |
| NER | Named-entity recognition | batch_69c6f9d9c55c8190841f3bf3225c096a |
completed | March 27, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69c6f4e2e42c8190afc802c4796c9cc2 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:53 p.m.