Triple

T36184668
Position Surface form Disambiguated ID Type / Status
Subject Volvo S70 E1046812 entity
Predicate platform P1292 FINISHED
Object Volvo P80 platform
The Volvo P80 platform is a front-wheel-drive automotive architecture used by Volvo in the 1990s for its mid-size models, including the 850 and its S/V/C70 successors.
E2173194 NE 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: Volvo P80 platform | Statement: [Volvo S70, platform, Volvo P80 platform]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Volvo P80 platform
Triple: [Volvo S70, platform, Volvo P80 platform]
Generated description
The Volvo P80 platform is a front-wheel-drive automotive architecture used by Volvo in the 1990s for its mid-size models, including the 850 and its S/V/C70 successors.

Provenance (5 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_69f76e3d4fbc81908c159c7beeb4ce00 completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7b513aef88190954d0c53eccd0b9e completed May 3, 2026, 8:50 p.m.
NED1 Entity disambiguation (via context triple) batch_6a39340fa3a88190890d04410862d012 completed June 22, 2026, 1:09 p.m.
NEDg Description generation batch_6a39358ef7f881908addabca93f79393 completed June 22, 2026, 1:15 p.m.
NED2 Entity disambiguation (via description) batch_6a39360370148190b76632b2d922404a completed June 22, 2026, 1:17 p.m.
Created at: May 3, 2026, 4:08 p.m.