Triple
T14618321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury Capri |
E343146
|
entity |
| Predicate | thirdGenerationEngine |
P115073
|
FINISHED |
| Object | 1.6L inline-four |
—
|
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.6L inline-four | Statement: [Mercury Capri, thirdGenerationEngine, 1.6L inline-four]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: thirdGenerationEngine Context triple: [Mercury Capri, thirdGenerationEngine, 1.6L inline-four]
-
A.
thirdGeneration
Indicates that one entity is the grandchild (third generation) relative to another entity in a lineage or succession.
-
B.
thirdGenerationProduction
Indicates that the subject is involved in producing or manufacturing items belonging to the third generation of a product, technology, or design series.
-
C.
thirdStageEngineType
Indicates the specific type or model of engine used in the third stage of a multi-stage launch vehicle or rocket.
-
D.
thirdGenerationStart
Indicates the point in time or event at which the third generation of a lineage, product line, or sequence begins.
-
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_69d822dec68081908c2553145c4051dc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb46550e48190af45f426f02579bb |
completed | April 14, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69de656f9f4c81909f815b6629a9ee39 |
completed | April 14, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:25 a.m.