Triple
T29868759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goro |
E758527
|
entity |
| Predicate | notableFinishers |
P207191
|
FINISHED |
| Object | Fatalities |
—
|
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: Fatalities | Statement: [Goro, notableFinishers, Fatalities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFinishers Context triple: [Goro, notableFinishers, Fatalities]
-
A.
hasNotableFinish
Indicates that something possesses a particularly distinctive, remarkable, or noteworthy ending or final phase.
-
B.
notableFinal
Indicates that an entity’s final work, appearance, or event is especially significant or well-known compared to its other endings.
-
C.
notableWinner
Indicates that the subject is a particularly distinguished or prominent winner of the referenced competition, award, or contest.
-
D.
notableLongRun
Indicates that an entity is recognized for having a particularly long or extended duration of continuous operation, performance, or existence.
-
E.
notableFirstWinner
Indicates that the subject is the first and notably recognized winner of the object (such as an award, competition, or title).
- 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_69f2245d0d7081909e37ee328542bcd7 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 5:52 p.m.