Triple

T20649396
Position Surface form Disambiguated ID Type / Status
Subject Beylik of Eretna E507446 entity
Predicate founder P104 FINISHED
Object Eretna 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: Eretna | Statement: [Beylik of Eretna, founder, Eretna]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Eretna
Context triple: [Beylik of Eretna, founder, Eretna]
  • A. Eretna chosen
    Eretna was a 14th-century Turkic-Mongol ruler in Anatolia who founded the Beylik of Eretna during the decline of the Ilkhanate.
  • B. Eotile
    Eotile is a lesser-known Central Tano language spoken in parts of West Africa, likely within the Ivory Coast region.
  • C. Raetihi
    Raetihi is a small rural town in New Zealand’s central North Island, known historically as a timber and farming service centre near the Tongariro National Park.
  • D. Nisaea
    Nisaea was the port town and harbor of ancient Megara in Greece, serving as its main maritime outlet on the Saronic Gulf.
  • E. Minturnae
    Minturnae was an ancient Roman town in Latium, Italy, situated along the Via Appia near the mouth of the Liris River and known for its strategic location and archaeological remains.
  • 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_69e0b4bf58c081908e52a4500e03ff83 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6af2076b48190b9c8afb4eac65f46 completed April 20, 2026, 10:56 p.m.
Created at: April 16, 2026, 11:43 a.m.