Triple

T3468271
Position Surface form Disambiguated ID Type / Status
Subject Iolcus E73188 entity
Predicate locatedIn P40 FINISHED
Object Magnesia E73188 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: Magnesia | Statement: [Iolcus, locatedIn, Magnesia]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Magnesia
Context triple: [Iolcus, locatedIn, Magnesia]
  • A. Magnesia chosen
    Magnesia is a historical coastal region in eastern Thessaly, Greece, known for its mountainous Pelion peninsula and ancient cities such as Iolcus and Demetrias.
  • B. Phosphoros
    Phosphoros is an epithet meaning “light-bringer,” associated with Hecate in her aspect as a luminous, guiding deity linked to the appearance of the morning star.
  • C. Calca
    Calca is a small Andean town in Peru’s Sacred Valley, known for its traditional Quechua culture and proximity to Inca archaeological sites.
  • D. Ankyra
    Ankyra is the ancient name of the city that later became Ankara, the capital of modern Turkey.
  • E. Tauresium
    Tauresium was an ancient settlement in the Balkans, traditionally identified as the birthplace of the Byzantine emperor Justinian I.
  • 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_69ad85b224d481908ff8be51338d24ff completed March 8, 2026, 2:20 p.m.
NER Named-entity recognition batch_69adbb11ec5881908347bf92883a25ee completed March 8, 2026, 6:08 p.m.
NED1 Entity disambiguation (via context triple) batch_69b3680763608190acdd146dc7c0b239 completed March 13, 2026, 1:27 a.m.
Created at: March 8, 2026, 3:17 p.m.