Triple

T23428479
Position Surface form Disambiguated ID Type / Status
Subject Sajik-dong E563258 entity
Predicate nearbyGovernmentDistrict P72400 FINISHED
Object central government complex area of Seoul LITERAL 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: central government complex area of Seoul | Statement: [Sajik-dong, nearbyGovernmentDistrict, central government complex area of Seoul]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nearbyGovernmentDistrict
Context triple: [Sajik-dong, nearbyGovernmentDistrict, central government complex area of Seoul]
  • A. locatedNearGovernmentDistrict chosen
    Indicates that one entity is situated close to or in the immediate vicinity of a government district.
  • B. governmentDistrict
    Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
  • C. governmentalDistrictOf
    Indicates that a governmental district is the administrative district to which a given entity belongs or in which it is located.
  • D. nearbyGovernorate
    Indicates that one governorate is geographically close to or adjacent to another governorate.
  • E. nearestDistrictHeadquarters
    Indicates that one location is the closest district headquarters to another specified place.
  • F. None of above.

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_69e24553980c8190bb66a2ae0bdab125 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1a54ba29881909945690496f28d65 completed April 29, 2026, 6:29 a.m.
PD Predicate disambiguation batch_69f061f92da081908e7f1d0cd1e9b01c completed April 28, 2026, 7:30 a.m.
Created at: April 17, 2026, 5:48 p.m.