Triple
T23178619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johnny Mantz |
E579084
|
entity |
| Predicate | usedTiresTypeInNotableWin |
P151238
|
FINISHED |
| Object | truck tires |
—
|
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: truck tires | Statement: [Johnny Mantz, usedTiresTypeInNotableWin, truck tires]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedTiresTypeInNotableWin Context triple: [Johnny Mantz, usedTiresTypeInNotableWin, truck tires]
-
A.
notableWinType
Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
-
B.
notableWin
Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
-
C.
championshipWinningCar
Indicates that a car is the specific vehicle that won a particular championship.
-
D.
hasNotableRide
Indicates that an entity is associated with a particularly remarkable or well-known ride or attraction.
-
E.
notableTournamentPerformance
Indicates that an entity achieved a significant or distinguished result or showing in a competitive tournament.
- 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_69e245fd2a388190b814c0dfa15f7148 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18f6cbe5481909444479b7eac47f7 |
completed | April 29, 2026, 4:56 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
| PDg | Predicate description generation | batch_69ef9b75e2708190ba48875e36f983bc |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 4:04 p.m.