Triple
T37190634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter P. Reuther Freeway |
E921441
|
entity |
| Predicate | commemorativeNameFor |
P154143
|
FINISHED |
| Object | Interstate 696 |
—
|
NE NERFINISHED |
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: Interstate 696 | Statement: [Walter P. Reuther Freeway, commemorativeNameFor, Interstate 696]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commemorativeNameFor Context triple: [Walter P. Reuther Freeway, commemorativeNameFor, Interstate 696]
-
A.
hasCommemorationName
chosen
Indicates that an entity has a specific name used to commemorate or honor a person, event, or concept.
-
B.
commemoratedFor
Indicates that one entity is honored, remembered, or celebrated because of a particular action, achievement, event, or characteristic associated with it.
-
C.
commemoratedBy
Indicates that something is honored, remembered, or celebrated through a particular action, event, object, or representation.
-
D.
memorialName
Indicates that a memorial is known by or designated with a particular name.
-
E.
eraCommemorated
Indicates that a particular era or historical period is honored, remembered, or marked by a commemorative act, object, or event.
- 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_69f76ea313a08190a54404cd1e47da90 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:15 p.m.