Triple

T15552773
Position Surface form Disambiguated ID Type / Status
Subject Poliochni E370792 entity
Predicate knownAs P39 FINISHED
Object Poliochne E370792 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: Poliochne | Statement: [Poliochni, knownAs, Poliochne]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Poliochne
Context triple: [Poliochni, knownAs, Poliochne]
  • A. Poliochni chosen
    Poliochni is an important prehistoric Aegean settlement on the island of Lemnos, often noted as one of the earliest known urban centers in Europe.
  • B. Hagioupolis
    Hagioupolis is an alternative historical name for the ancient city of Cyrrhus in northern Syria, known as an important center in the early Christian and Byzantine periods.
  • C. Polykastro
    Polykastro is a town in northern Greece located in the Kilkis regional unit, known for its agricultural surroundings and proximity to the border with North Macedonia.
  • D. Charioupolis
    Charioupolis is a district of the city of Kalamaria in the Thessaloniki urban area of northern Greece.
  • E. Troesmis
    Troesmis was an ancient Roman military and urban settlement in the province of Moesia, strategically located near the Danube River in what is now Romania.
  • 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_69d85cc6cf40819091f4a5facee1ebe6 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04a9551288190a583e8291c35f521 completed April 16, 2026, 2:33 a.m.
NED1 Entity disambiguation (via context triple) batch_69ff4560008c81908ebd278c3dc45045 completed May 9, 2026, 2:32 p.m.
Created at: April 10, 2026, 4:08 a.m.