Triple

T20159462
Position Surface form Disambiguated ID Type / Status
Subject Maribor railway station E491664 entity
Predicate locatedIn P40 FINISHED
Object Maribor 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: Maribor | Statement: [Maribor railway station, locatedIn, Maribor]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Maribor
Context triple: [Maribor railway station, locatedIn, Maribor]
  • A. Maribor chosen
    Maribor is Slovenia’s second-largest city, known for its historic old town, wine culture, and the world’s oldest grapevine.
  • B. Celje
    Celje is a historic city in eastern Slovenia known for its medieval castle and former prominence as a regional political and economic center.
  • C. Ljubljana
    Ljubljana is the capital and largest city of Slovenia, known for its picturesque old town, Baroque and Art Nouveau architecture, and vibrant cultural scene along the Ljubljanica River.
  • D. Kranj
    Kranj is a historic industrial city in northwestern Slovenia, known as a regional economic center and gateway to the Slovenian Alps.
  • E. Šempeter pri Gorici
    Šempeter pri Gorici is a small town in western Slovenia near the Italian border, known for its close ties to the city of Nova Gorica and the cross-border Gorizia region.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e667e37c8c8190827839291027d9e2 completed April 20, 2026, 5:52 p.m.
Created at: April 11, 2026, 11:34 p.m.