Triple

T4247549
Position Surface form Disambiguated ID Type / Status
Subject Peugeot 205 E95563 entity
Predicate GTIVariantDisplacement P7998 FINISHED
Object 1.6-litre petrol engine 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.6-litre petrol engine | Statement: [Peugeot 205, GTIVariantDisplacement, 1.6-litre petrol engine]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: GTIVariantDisplacement
Context triple: [Peugeot 205, GTIVariantDisplacement, 1.6-litre petrol engine]
  • A. displacementVariant
    Indicates a relationship where one entity is an alternative or modified form of another that differs specifically in its spatial position or displacement.
  • B. engineDisplacement chosen
    Indicates the total volume swept by all the pistons inside an engine’s cylinders during one complete cycle.
  • C. carTypeVariant
    Indicates that one car type is a specific variant or version of another car type.
  • D. displacementRange
    Indicates the minimum and maximum extent of positional change or movement that an entity can undergo or exhibits.
  • E. displacementClass
    Indicates the category or type of physical displacement associated with an entity or event, typically grouping similar kinds or magnitudes of movement into a common class.
  • 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_69b3453d91548190b4d4ef8fe52aa2ac completed March 12, 2026, 10:59 p.m.
NER Named-entity recognition batch_69b34e9cb71481909b4baa370193148f completed March 12, 2026, 11:39 p.m.
PD Predicate disambiguation batch_69b347f587148190a1830503459939b6 completed March 12, 2026, 11:10 p.m.
Created at: March 12, 2026, 11:05 p.m.