Triple
T7459430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VISTA |
E176206
|
entity |
| Predicate | officialInaugurationDate |
P2496
|
FINISHED |
| Object | 10 December 2009 |
—
|
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: 10 December 2009 | Statement: [VISTA, officialInaugurationDate, 10 December 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialInaugurationDate Context triple: [VISTA, officialInaugurationDate, 10 December 2009]
-
A.
inaugurationDate
chosen
Indicates the date on which an official ceremony formally installs a person into a specific office or position.
-
B.
originalInaugurationDate
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
-
C.
inaugurationDay
Indicates the specific day on which a formal ceremony is held to induct someone into an official position or office.
-
D.
inauguralEventDate
Indicates the calendar date on which an entity’s first or inaugural event took place.
-
E.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d332d08190a05c92a00ed09ac6 |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f039f7248190bb4183f97b605763 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:37 p.m.