Triple

T17631363
Position Surface form Disambiguated ID Type / Status
Subject Troy (region) E429982 entity
Predicate hasHistoricalSite P1098 FINISHED
Object Hisarlik 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: Hisarlik | Statement: [Troy (region), hasHistoricalSite, Hisarlik]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hisarlik
Context triple: [Troy (region), hasHistoricalSite, Hisarlik]
  • A. Hisarlik chosen
    Hisarlik is an archaeological mound in northwestern Turkey widely identified as the site of ancient Troy, extensively excavated by Heinrich Schliemann.
  • B. Hisar
    Hisar is a major city in the Indian state of Haryana known for its historical significance, agricultural research institutions, and role as a regional commercial center.
  • C. Uçhisar
    Uçhisar is a small town in Turkey’s Cappadocia region, best known for its towering rock castle and panoramic views over the surrounding fairy-chimney landscape.
  • D. Qala
    Qala is a small village on the eastern tip of the Maltese island of Gozo, known for its scenic coastal views and traditional rural character.
  • E. Qalat
    Qalat is a key urban center and provincial capital in southern Afghanistan, known for its strategic location and historical fortifications.
  • 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_69d889e37f308190a6aa0a69daff86c7 completed April 10, 2026, 5:25 a.m.
NER Named-entity recognition batch_69e46dc192dc8190854f1fe5d5ed696a completed April 19, 2026, 5:53 a.m.
Created at: April 10, 2026, 5:52 a.m.