Triple

T18162560
Position Surface form Disambiguated ID Type / Status
Subject Battle of Dorylaeum E434802 entity
Predicate location P40 FINISHED
Object Dorylaeum 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: Dorylaeum | Statement: [Battle of Dorylaeum, location, Dorylaeum]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Dorylaeum
Context triple: [Battle of Dorylaeum, location, Dorylaeum]
  • A. Dorylaeum chosen
    Dorylaeum was an ancient city in Phrygia, in what is now northwestern Turkey, known as a strategic and military center in classical and medieval times.
  • B. Amaliapoli
    Amaliapoli is a small coastal town in central Greece known for its scenic beaches and tranquil setting on the Pagasetic Gulf.
  • C. Trebizond mint
    The Trebizond mint was a provincial Ottoman coin-producing facility located in the historic Black Sea port city of Trebizond (modern Trabzon).
  • D. Nichoria
    Nichoria is an important archaeological site in Messenia, Greece, known for its evidence of settlement continuity and social organization during the Greek Dark Ages.
  • E. Chrysopolis
    Chrysopolis was an ancient town located on the Asian side of the Bosporus, opposite Byzantium (later Constantinople), known historically as a strategic crossing and military site.
  • 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_69d8b90b7a188190b3fc7b8d4a6cd20a completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dec32530819099d906640a07e92c completed April 19, 2026, 1:55 p.m.
Created at: April 10, 2026, 10:30 a.m.