Triple
T3803835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citroën Saxo |
E91754
|
entity |
| Predicate | hotHatchVariant |
P12592
|
FINISHED |
| Object | Saxo VTS 1.6 16V |
—
|
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: Saxo VTS 1.6 16V | Statement: [Citroën Saxo, hotHatchVariant, Saxo VTS 1.6 16V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hotHatchVariant Context triple: [Citroën Saxo, hotHatchVariant, Saxo VTS 1.6 16V]
-
A.
turbochargedVariant
Indicates that one entity is a turbocharged version or configuration of another entity.
-
B.
notableHighPerformanceVariant
chosen
Indicates that an entity is recognized as a particularly high-performance version or variant of another entity.
-
C.
wheelbaseVariantOf
Indicates a relationship where one vehicle’s wheelbase configuration is a variant or modified version of another vehicle’s wheelbase.
-
D.
notableRacingVariant
Indicates that one entity is a particularly recognized or distinguished racing-specific version or trim of another entity.
-
E.
winnerPowertrainType
Indicates the type of powertrain used by the entity that is identified as the winner in a given context or competition.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.