Triple
T8576269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford Thunderbird |
E203054
|
entity |
| Predicate | seventhGenerationStart |
P43270
|
FINISHED |
| Object | 1977 |
—
|
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: 1977 | Statement: [Ford Thunderbird, seventhGenerationStart, 1977]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seventhGenerationStart Context triple: [Ford Thunderbird, seventhGenerationStart, 1977]
-
A.
seventhGenerationStartYear
chosen
Indicates the calendar year in which the seventh generation of a series, lineage, or sequence begins.
-
B.
seventhGenerationEndYear
Indicates the year in which the seventh generation of something (e.g., a product line, lineage, or series) comes to an end.
-
C.
thirdGenerationStart
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
D.
secondGenerationStartYear
Indicates the calendar year in which the second generation of something (e.g., a product, model, or series) begins.
-
E.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
- 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_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_69cbd11856048190a1ce4b83a38f6965 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:21 p.m.