Triple

T15841867
Position Surface form Disambiguated ID Type / Status
Subject Kockums Mekaniska Verkstad E384119 entity
Predicate locatedIn P40 FINISHED
Object Scania E138516 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: Scania | Statement: [Kockums Mekaniska Verkstad, locatedIn, Scania]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Scania
Context triple: [Kockums Mekaniska Verkstad, locatedIn, Scania]
  • A. Scania
    Scania is a Swedish manufacturer renowned for its heavy trucks, buses, and industrial and marine engines.
  • B. Scania chosen
    Scania is a historical province in southern Sweden known for its fertile farmland, coastal landscapes, and former status as part of Denmark.
  • C. Volvo Group
    Volvo Group is a Swedish multinational manufacturing company best known for producing trucks, buses, construction equipment, and marine and industrial engines.
  • D. Neoplan
    Neoplan is a German bus and coach manufacturer renowned for its innovative, high-end touring and city buses.
  • E. Volvo Cars
    Volvo Cars is a Swedish automotive manufacturer known for its focus on safety, practical design, and premium vehicles.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d86da34c888190976e06c4019d415a completed April 10, 2026, 3:25 a.m.
NER Named-entity recognition batch_69e142e88ff08190a1035269e8fdaa6a completed April 16, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69ffa13eab4881908794104508ba53af completed May 9, 2026, 9:03 p.m.
Created at: April 10, 2026, 4:50 a.m.