Triple
T18286630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reno Arch |
E438000
|
entity |
| Predicate | currentVersionInaugurated |
P35486
|
FINISHED |
| Object | 1987 |
—
|
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: 1987 | Statement: [Reno Arch, currentVersionInaugurated, 1987]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentVersionInaugurated Context triple: [Reno Arch, currentVersionInaugurated, 1987]
-
A.
inauguratedBefore
Indicates that one entity’s inauguration occurred earlier in time than another entity’s inauguration.
-
B.
inauguratedWith
Indicates that an event, position, or institution was formally initiated or opened through a specific ceremony, action, or accompanying element.
-
C.
inauguratedFor
Indicates that a formal ceremony or event was held to officially begin or dedicate something specifically for a particular entity, role, or purpose.
-
D.
inauguratedReignOf
Indicates that one entity formally began or initiated the period of rule or reign of another entity.
-
E.
originalInaugurationDate
chosen
Indicates the date on which an entity (such as an office, institution, or facility) was first formally inaugurated or put into official operation.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fa2f308190a4744a4ed630b8d9 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.