Triple

T22287237
Position Surface form Disambiguated ID Type / Status
Subject Sevel Sud joint venture E550894 entity
Predicate hasAbbreviation P43 FINISHED
Object Sevel Sud NE NERFINISHED

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 Sud | Statement: [Sevel Sud joint venture, hasAbbreviation, Sevel Sud]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Sevel Sud
Context triple: [Sevel Sud joint venture, hasAbbreviation, Sevel Sud]
  • A. Sevel Sud chosen
    Sevel Sud is an Italian automotive manufacturing company best known for producing light commercial vehicles at the Val di Sangro plant in Abruzzo.
  • B. Sulem
    Sulem is a modern locality believed by some scholars to correspond to the ancient biblical town of Shunem in present-day Israel.
  • C. Suhre
    The Suhre is a river in Switzerland that flows through the cantons of Lucerne and Aargau before joining the Aare.
  • D. Sääre
    Sääre is a small village in southwestern Estonia, located on the Sõrve Peninsula of Saaremaa Island and known for its lighthouse and coastal scenery.
  • E. Sulzeer
    Sulzeer is the given first name of former English professional footballer and central defender Sol Campbell.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e11e44d538819097c6b8f333af3352 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f1560896348190985725ac8ad406b3 completed April 29, 2026, 12:51 a.m.
Created at: April 16, 2026, 8:40 p.m.