Triple

T23259287
Position Surface form Disambiguated ID Type / Status
Subject Seocho-gu Office E581959 entity
Predicate servesAdministrativeDistrict P145445 FINISHED
Object Seocho-gu 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: Seocho-gu | Statement: [Seocho-gu Office, servesAdministrativeDistrict, Seocho-gu]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: servesAdministrativeDistrict
Context triple: [Seocho-gu Office, servesAdministrativeDistrict, Seocho-gu]
  • A. administrativeDistrictOf
    Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
  • B. administrativeDistricts
    Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
  • C. administrativeCouncilArea
    Indicates that one entity is an administrative council area within which the other entity is located or governed.
  • D. servesGovernmentDistrict
    Indicates that an entity provides official services or representation to a specific government district.
  • E. servesAsMunicipalAuthorityFor chosen
    Indicates that an entity functions as the official municipal governing or administrative authority for a specified locality or jurisdiction.
  • 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_69e246079f58819085eaa9c260906880 completed April 17, 2026, 2:39 p.m.
NER Named-entity recognition batch_69f194c7ec148190b01fd215a0c1daa1 completed April 29, 2026, 5:19 a.m.
PD Predicate disambiguation batch_69effce4d704819092826931d430e8c4 completed April 28, 2026, 12:18 a.m.
Created at: April 17, 2026, 4:11 p.m.