Triple
T5006316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Koch Queensboro Bridge |
E112501
|
entity |
| Predicate | officialRenaming |
P60794
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Ed Koch Queensboro Bridge, officialRenaming, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officialRenaming Context triple: [Ed Koch Queensboro Bridge, officialRenaming, 2011]
-
A.
renamingAnnouncedBy
Indicates that an entity’s change of name has been publicly announced or made known by another specified entity.
-
B.
officialName
Indicates the formally recognized name assigned to an entity by an authoritative body or source.
-
C.
renamedDueTo
Indicates that one entity was renamed as a consequence of another specified cause, event, or condition.
-
D.
reformName
Indicates that an entity has undergone a reform or change resulting in a new name or designation.
-
E.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
- 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_69bd4433d0b08190877e83959ef40d81 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd730a7590819088ab8d49c5c88c2f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
| PDg | Predicate description generation | batch_69bd73089f548190834103366e24ab40 |
completed | March 20, 2026, 4:17 p.m. |
Created at: March 20, 2026, 1:35 p.m.