Triple
T36114988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota MR2 |
E1044594
|
entity |
| Predicate | thirdGenerationProductionEnd |
P25156
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Toyota MR2, thirdGenerationProductionEnd, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationProductionEnd Context triple: [Toyota MR2, thirdGenerationProductionEnd, 2007]
-
A.
thirdGenerationProduction
Indicates that the subject is involved in producing or manufacturing items belonging to the third generation of a product, technology, or design series.
-
B.
thirdGenerationEnd
chosen
Indicates that a third generation in a sequence, lineage, or process has reached its endpoint or conclusion.
-
C.
thirdGenerationStart
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
D.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
-
E.
thirdGenerationEngine
Indicates that the engine belongs to the third generation in a defined sequence of engine designs or technological iterations.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 3, 2026, 4:08 p.m.