Triple
T2223251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elizabeth Tower |
E48188
|
entity |
| Predicate | inauguratedInYear |
P4218
|
FINISHED |
| Object | 1859 |
—
|
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: 1859 | Statement: [Elizabeth Tower, inauguratedInYear, 1859]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inauguratedInYear Context triple: [Elizabeth Tower, inauguratedInYear, 1859]
-
A.
inaugurationYear
chosen
Indicates the calendar year in which an entity was formally inaugurated or officially brought into operation.
-
B.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
-
C.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
-
D.
inaugurationDate
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
E.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
- 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_69a88aa1ee708190862c8c378c41e9eb |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc03d1df88190950c691a4c246bd1 |
completed | March 7, 2026, 6:05 a.m. |
| PD | Predicate disambiguation | batch_69abbdac31d8819092d17815e11921e9 |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:47 p.m.