Triple
T21428758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford GT40 |
E528627
|
entity |
| Predicate | 1966Result |
P374
|
FINISHED |
| Object | 1-2-3 finish at 24 Hours of Le Mans |
—
|
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: 1-2-3 finish at 24 Hours of Le Mans | Statement: [Ford GT40, 1966Result, 1-2-3 finish at 24 Hours of Le Mans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 1966Result Context triple: [Ford GT40, 1966Result, 1-2-3 finish at 24 Hours of Le Mans]
-
A.
season1966_67Outcome
Indicates the outcome or result associated with the 1966–67 season of a competition or event.
-
B.
seasonResult2016
Indicates the outcome or performance result associated with an entity for the 2016 season.
-
C.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
D.
result
chosen
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
E.
resultsReleasedIn
Indicates that the results of an event, process, or evaluation were made publicly available in a specified location, medium, or context.
- 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_69e0c455f3688190810bc96365791b0f |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ee813db52c8190ac933bc6ec4dbf77 |
completed | April 26, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69e61639ee288190889ffd500d1260f6 |
completed | April 20, 2026, 12:04 p.m. |
Created at: April 16, 2026, 5:49 p.m.