Triple

T21746559
Position Surface form Disambiguated ID Type / Status
Subject Citroën Dispatch E536802 entity
Predicate heightOptions P145212 FINISHED
Object multiple roof heights available 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: multiple roof heights available | Statement: [Citroën Dispatch, heightOptions, multiple roof heights available]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: heightOptions
Context triple: [Citroën Dispatch, heightOptions, multiple roof heights available]
  • A. heightContext
    Indicates a contextual or situational relationship that specifies how an entity’s height is defined, measured, or interpreted in a particular setting or frame of reference.
  • B. heightDescription
    Indicates how tall an entity is, typically expressed in descriptive or qualitative terms rather than a precise measurement.
  • C. hasHeight
    Indicates that one entity possesses a specific vertical measurement or stature.
  • D. heightClass
    Indicates the categorical height level or range to which an entity is assigned (e.g., short, medium, tall).
  • E. heightReference
    Indicates that one entity’s height is being measured, compared, or defined relative to another specified reference point or standard.
  • 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_69e0c46df5448190b4322127ffc4c690 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f01a771b908190886cade242e263e4 completed April 28, 2026, 2:24 a.m.
PD Predicate disambiguation batch_69e6969c16fc8190b5126c169317d85d completed April 20, 2026, 9:11 p.m.
PDg Predicate description generation batch_69e69f3ed4408190a4a78410bf660c44 completed April 20, 2026, 9:48 p.m.
Created at: April 16, 2026, 6:49 p.m.