Triple

T14558422
Position Surface form Disambiguated ID Type / Status
Subject Jos East E341602 entity
Predicate administrativeHeadquarters P62 FINISHED
Object Angware E1107388 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: Angware | Statement: [Jos East, administrativeHeadquarters, Angware]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Angware
Context triple: [Jos East, administrativeHeadquarters, Angware]
  • A. Angware chosen
    Angware is a town in Plateau State, Nigeria, serving as the administrative center of Jos East Local Government Area.
  • B. Sha Tau Kok
    Sha Tau Kok is a frontier town in northeastern Hong Kong known for its restricted border area status and proximity to the boundary with mainland China.
  • C. Tai Wai
    Tai Wai is a residential and transport hub area in Hong Kong’s New Territories, known for its major railway interchange and proximity to Sha Tin.
  • D. Hagonoy
    Hagonoy is a coastal agricultural municipality in the province of Davao del Sur in the Philippines.
  • E. Hagonoy
    Hagonoy is a coastal municipality in the province of Bulacan in the Philippines, known for its fishing industry and aquaculture.
  • 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_69d822db9c8481908213ceb39585f792 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb3881b788190922932fb8ff81160 completed April 14, 2026, 9:37 p.m.
NED1 Entity disambiguation (via context triple) batch_69fd94b1760481909119db555fd05429 completed May 8, 2026, 7:45 a.m.
Created at: April 10, 2026, 1:23 a.m.