Triple
T25907749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ongjin-eup |
E652799
|
entity |
| Predicate | locatedInCountyLevelDivision |
P35926
|
FINISHED |
| Object | Ongjin County |
—
|
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: Ongjin County | Statement: [Ongjin-eup, locatedInCountyLevelDivision, Ongjin County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInCountyLevelDivision Context triple: [Ongjin-eup, locatedInCountyLevelDivision, Ongjin County]
-
A.
locatedInCountySeatOfCounty
Indicates that one entity is located in the county seat city or town of the specified county.
-
B.
locatedInCountyRegion
chosen
Indicates that one entity is geographically situated within the boundaries of a specific county or county-level region.
-
C.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
D.
locatedInPrefectureLevel
Indicates that one entity is geographically situated within, and administratively belongs to, a specific prefecture-level jurisdiction.
-
E.
isLocatedInSubdivision
Indicates that one place or entity is situated within a more specific administrative or geographic subdivision of another area.
- 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_69e7ab3d3f8481909bc53ed64c06af33 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
Created at: April 22, 2026, 8:27 a.m.