Triple
T6868253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Avenue |
E158469
|
entity |
| Predicate | openedAsGrandAvenue |
P74209
|
FINISHED |
| Object | 2017 |
—
|
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: 2017 | Statement: [Grand Avenue, openedAsGrandAvenue, 2017]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedAsGrandAvenue Context triple: [Grand Avenue, openedAsGrandAvenue, 2017]
-
A.
openedRouteThrough
Indicates that one entity has created or established a passage, connection, or pathway that allows movement or access through another entity or area.
-
B.
openedAsCeremonialRoute
Indicates that a route was inaugurated or made accessible specifically for use in ceremonial or formal events.
-
C.
openedAsTollBridge
Indicates that a bridge was initially opened to traffic as a toll bridge, requiring users to pay a fee to cross.
-
D.
openingTo
Indicates that one entity serves as an entrance, access point, or passage leading into or toward another entity.
-
E.
openedAsSubway
Indicates that a transportation facility or line originally began operation specifically as a subway service.
- F. None of above. chosen
Provenance (4 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6da3b5510819093c5893ea92ac025 |
completed | March 27, 2026, 7:27 p.m. |
Created at: March 27, 2026, 2:21 p.m.