Triple

T10705990
Position Surface form Disambiguated ID Type / Status
Subject Stone Bridge E252405 entity
Predicate locatedIn P40 FINISHED
Object Skopje E33001 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: Skopje | Statement: [Stone Bridge, locatedIn, Skopje]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Skopje
Context triple: [Stone Bridge, locatedIn, Skopje]
  • A. Skopje chosen
    Skopje is the capital and largest city of North Macedonia, known for its historic Ottoman and Byzantine heritage alongside extensive modern redevelopment.
  • B. Tetovo
    Tetovo is a city in northwestern North Macedonia known for its multicultural population, Ottoman-era architecture, and proximity to the Šar Mountains.
  • C. Rabotnički Skopje
    Rabotnički Skopje is a professional football club from Skopje, North Macedonia, known for competing in the country’s top division and developing notable players.
  • D. Skopun
    Skopun is a small coastal village on the Faroe Islands’ island of Sandoy, known for its fishing heritage and scenic North Atlantic surroundings.
  • E. Mitrovica
    Mitrovica is a divided city in northern Kosovo known for its ethnic tensions and strategic importance as a regional industrial and mining center.
  • 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_69d6aa5cbabc8190973e683950d89faf completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6fddfbed48190810bb3faee473fde completed April 9, 2026, 1:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69d998fe56dc8190ae0c987b28ec6206 completed April 11, 2026, 12:42 a.m.
Created at: April 8, 2026, 9:12 p.m.