Triple
T21869851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naju |
E539972
|
entity |
| Predicate | distanceFromGwangju |
P145987
|
FINISHED |
| Object | approximately 20 km southwest |
—
|
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: approximately 20 km southwest | Statement: [Naju, distanceFromGwangju, approximately 20 km southwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromGwangju Context triple: [Naju, distanceFromGwangju, approximately 20 km southwest]
-
A.
distanceToSeoul
Indicates the measured or estimated spatial distance between a given entity’s location and the city of Seoul.
-
B.
distanceFromKochi_km
Indicates the physical distance, measured in kilometers, between a given location and Kochi.
-
C.
distanceToKoreanPeninsula
Indicates the measured or estimated spatial distance between a given entity or location and the Korean Peninsula.
-
D.
distanceToShinjukuStation_km
Indicates the physical distance, measured in kilometers, between a given place and Shinjuku Station.
-
E.
directionFromSeoul
Indicates the cardinal or relative compass direction in which an entity is located when measured from Seoul.
- 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_69e0c478f59081909d54302b57fc1ce3 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f0f334362c819094af465ee57b47e6 |
completed | April 28, 2026, 5:49 p.m. |
| PD | Predicate disambiguation | batch_69e6be9394f88190945ddd1dc004d29d |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6d054737081908aa7112975b77475 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 6:57 p.m.