Triple

T16393092
Position Surface form Disambiguated ID Type / Status
Subject Hyampolis E398103 entity
Predicate ancientName P2834 FINISHED
Object Hyampolis E398103 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: Hyampolis | Statement: [Hyampolis, ancientName, Hyampolis]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Hyampolis
Context triple: [Hyampolis, ancientName, Hyampolis]
  • A. Hyampolis chosen
    Hyampolis was an ancient Greek city in the region of Phocis, known as a strategic and religious center in central Greece.
  • B. Eleutherae
    Eleutherae was an ancient Greek city on the border between Attica and Boeotia, known for its sanctuary of Dionysus and its strategic location near Mount Cithaeron.
  • C. Coronea
    Coronea was an ancient city of Boeotia in central Greece, known for its strategic location and role in several classical Greek battles.
  • D. Argive Heraion
    The Argive Heraion is an ancient sanctuary in the Argolid region of Greece dedicated to the goddess Hera, notable as one of the most important religious centers of the classical Greek world.
  • 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_69d87f2880b48190ae1a9673a3bbef80 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e326447a7481909feac905edc707ec completed April 18, 2026, 6:35 a.m.
NED1 Entity disambiguation (via context triple) batch_6a004f439d048190bf779cb263b7c7a7 completed May 10, 2026, 9:26 a.m.
Created at: April 10, 2026, 5:08 a.m.