Triple
T13291623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaguar XJ220 |
E316571
|
entity |
| Predicate | productionEngineChangeFromConcept |
P98973
|
FINISHED |
| Object | V12 replaced by twin-turbo V6 |
—
|
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: V12 replaced by twin-turbo V6 | Statement: [Jaguar XJ220, productionEngineChangeFromConcept, V12 replaced by twin-turbo V6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionEngineChangeFromConcept Context triple: [Jaguar XJ220, productionEngineChangeFromConcept, V12 replaced by twin-turbo V6]
-
A.
engineChanges
chosen
Indicates that an entity undergoes a modification or replacement of its engine.
-
B.
fromProduction
Indicates that something originates from, is derived from, or is produced by a particular production process, source, or facility.
-
C.
gameEngineModification
Indicates a relationship where an entity alters, extends, or customizes the functionality or behavior of a game engine.
-
D.
developedEngine
Indicates that one entity created, designed, or engineered an engine for another entity or purpose.
-
E.
replacesConcept
Indicates that one concept takes the place of, or supersedes, another concept in a given context or system.
- 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_69d806b349908190a9a61dd9323bf153 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6893708190aeebf4c47386cff7 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:27 p.m.