Triple
T6774659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulsan-gwangyeoksi |
E155125
|
entity |
| Predicate | hasAdministrativeDistrictType |
P35772
|
FINISHED |
| Object | Gu |
—
|
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: Gu | Statement: [Ulsan-gwangyeoksi, hasAdministrativeDistrictType, Gu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAdministrativeDistrictType Context triple: [Ulsan-gwangyeoksi, hasAdministrativeDistrictType, Gu]
-
A.
hasAdministrativeArea
Indicates that one entity serves as the governing or jurisdictional area responsible for administering another entity.
-
B.
usesAdministrativeDivisionType
chosen
Indicates that one entity employs or applies a particular type of administrative division as part of its territorial or organizational structure.
-
C.
administrativeDistrictOf
Indicates that one entity serves as the administrative district or jurisdictional area governing or encompassing another entity.
-
D.
administrativeDistricts
Indicates that one entity serves as an administrative district or subdivision governed or managed by another entity.
-
E.
containsAdministrativeTerritory
Indicates that one administrative unit geographically or jurisdictionally includes another administrative territory within its boundaries.
- 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_69c68812ef7c819099369f51febb725c |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d24ddaf08190baffbff991eeb458 |
completed | March 27, 2026, 6:54 p.m. |
| PD | Predicate disambiguation | batch_69c6d094105881909c5806eb4afa6306 |
completed | March 27, 2026, 6:46 p.m. |
Created at: March 27, 2026, 2:13 p.m.