Triple
T23904029
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1976 World Rally Championship season |
E601133
|
entity |
| Predicate | thirdPlaceManufacturer |
P154027
|
FINISHED |
| Object | Ford |
—
|
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: Ford | Statement: [1976 World Rally Championship season, thirdPlaceManufacturer, Ford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdPlaceManufacturer Context triple: [1976 World Rally Championship season, thirdPlaceManufacturer, Ford]
-
A.
thirdPlaceProfessionalPartner
Indicates that one entity is the professional partner who finished in third place in a specified event or ranking relative to another entity.
-
B.
thirdPlaceRank
Indicates that an entity holds the third position in a ranking or ordered list relative to others.
-
C.
thirdGenerationMarketedAs
Indicates that something is promoted or labeled as being in its third generation within a series or product line.
-
D.
thirdPlaceTeam
Indicates that a team finished in third place in a competition, league, or ranking.
-
E.
thirdElement
Indicates that one entity is the third element in an ordered sequence or tuple associated with 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde0674c8190a5e1ce0315ae83cd |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f167dca3608190ace9d2eef56b2af6 |
completed | April 29, 2026, 2:07 a.m. |
Created at: April 17, 2026, 8:26 p.m.