Triple
T28598535
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ironworkers Memorial Second Narrows Crossing |
E723841
|
entity |
| Predicate | hasCommemorativeNameChangeReason |
P156911
|
FINISHED |
| Object | 1958 construction disaster |
—
|
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: 1958 construction disaster | Statement: [Ironworkers Memorial Second Narrows Crossing, hasCommemorativeNameChangeReason, 1958 construction disaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCommemorativeNameChangeReason Context triple: [Ironworkers Memorial Second Narrows Crossing, hasCommemorativeNameChangeReason, 1958 construction disaster]
-
A.
hasHistoricalNameChangeReason
Indicates that there is a specific reason or cause associated with a change in an entity’s historical name.
-
B.
renamedToCommemorate
chosen
Indicates that something has been given a new name specifically to honor or memorialize a person, event, or entity.
-
C.
hasCommemorationName
Indicates that an entity has a specific name used to commemorate or honor a person, event, or concept.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
تاريخ_تغيير_الاسم
Indicates the date on which an entity’s name was changed.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69ffcc6182b48190afb598ced6500e66 |
completed | May 10, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69ffcbb363748190bc6f8d038fba44ff |
completed | May 10, 2026, 12:05 a.m. |
Created at: April 28, 2026, 4:23 a.m.