Triple

T24683548
Position Surface form Disambiguated ID Type / Status
Subject Sevel platform E611215 entity
Predicate marketedAs P1395 FINISHED
Object Sevel LCV platform
The Sevel LCV platform is a shared light commercial vehicle architecture co-developed by major European automakers to underpin a range of vans and utility vehicles.
E1648586 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: Sevel LCV platform | Statement: [Sevel platform, marketedAs, Sevel LCV 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: Sevel LCV platform
Triple: [Sevel platform, marketedAs, Sevel LCV platform]
Generated description
The Sevel LCV platform is a shared light commercial vehicle architecture co-developed by major European automakers to underpin a range of vans and utility vehicles.

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_69e2c4d5c2dc8190ac857dea25ec6ce9 completed April 17, 2026, 11:40 p.m.
NER Named-entity recognition batch_69f40fc2c040819090f5e3e51a9d0b18 completed May 1, 2026, 2:28 a.m.
NED1 Entity disambiguation (via context triple) batch_6a100ffc3fd081909bcf8805b125240e completed May 22, 2026, 8:12 a.m.
NEDg Description generation batch_6a10136aa8948190b19d212e087b3f35 completed May 22, 2026, 8:27 a.m.
NED2 Entity disambiguation (via description) batch_6a1015013f6c8190be31319e5c05c3f4 completed May 22, 2026, 8:34 a.m.
Created at: April 18, 2026, 3:16 a.m.