Triple
T8576278
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Thunderbird |
E203054
|
entity |
| Predicate | eleventhGenerationEnd |
P82940
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [Ford Thunderbird, eleventhGenerationEnd, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eleventhGenerationEnd Context triple: [Ford Thunderbird, eleventhGenerationEnd, 2005]
-
A.
finalGenerationOf
Indicates that one entity represents the last or ultimate generation or iteration in a sequence or lineage of another entity.
-
B.
firstGenerationEnd
Indicates the point in time or event at which the first generation in a sequence, lineage, or process concludes.
-
C.
fourthGenerationEnd
Indicates that a lineage, process, or sequence has reached the end of its fourth generation.
-
D.
secondGenerationEnd
Indicates the point in time or event at which the second generation of a lineage, process, or system concludes.
-
E.
thirdGenerationEnd
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
- 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_69ca8328ebe481909a8c038fa79959b4 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbea9638c081909a537cc44e485bee |
completed | March 31, 2026, 3:39 p.m. |
| PD | Predicate disambiguation | batch_69cbd11b13108190b07f8f161425a585 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:21 p.m.