Triple
T21622800
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cheonggyecheon Stream |
E533618
|
entity |
| Predicate | urbanDistrictsTraversed |
P144817
|
FINISHED |
| Object | Jongno-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: Jongno-gu | Statement: [Cheonggyecheon Stream, urbanDistrictsTraversed, Jongno-gu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urbanDistrictsTraversed Context triple: [Cheonggyecheon Stream, urbanDistrictsTraversed, Jongno-gu]
-
A.
cityDistrictLevel
Indicates that one administrative unit is a district-level subdivision within a given city in the territorial hierarchy.
-
B.
targetCityDistrict
Indicates that one entity is a specific city district that serves as the target or destination in relation to another entity.
-
C.
cityAccess
Indicates that an entity has permission or the ability to enter, use, or reach a particular city.
-
D.
directionWithinCity
Indicates a directional relationship specifying where something is located or oriented within the boundaries of a particular city.
-
E.
urbanDistrictType
Indicates the classification of an urban district according to its specific type or category within an administrative or planning system.
- F. None of above. chosen
Provenance (4 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_69e0c464fba881908d0ff2ac80511ce1 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bb0c42c8190997fbeb7a764d60e |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:34 p.m.