Triple

T23150710
Position Surface form Disambiguated ID Type / Status
Subject Mandisha E578313 entity
Predicate locatedInTimeZone P109 FINISHED
Object Africa/Cairo 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: Africa/Cairo | Statement: [Mandisha, locatedInTimeZone, Africa/Cairo]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Africa/Cairo
Context triple: [Mandisha, locatedInTimeZone, Africa/Cairo]
  • A. Africa/Cairo chosen
    Africa/Cairo is the time zone corresponding to Eastern European Time (UTC+2) used primarily in Egypt, including its capital, Cairo.
  • B. Tanta
    Tanta is a small Andean town in Peru known for its high-altitude landscapes and traditional rural life within the Nor Yauyos-Cochas scenic reserve.
  • C. Tanta
    Tanta is a major city in northern Egypt that serves as an important commercial and transportation hub in the Nile Delta.
  • D. AFRIQIYAH
    AFRIQIYAH is the radio callsign used by Afriqiyah Airways, the state-owned flag carrier airline of Libya.
  • E. Africa/Casablanca
    Africa/Casablanca is the IANA time zone identifier corresponding to the standard time observed in Casablanca, Morocco.
  • 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_69e245fb8de081908f0eba7b5fd75bc4 completed April 17, 2026, 2:38 p.m.
NER Named-entity recognition batch_69f18ed1a258819091ce86dbd1c51e46 completed April 29, 2026, 4:53 a.m.
Created at: April 17, 2026, 4:01 p.m.