Triple
T32312911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Osan |
E825548
|
entity |
| Predicate | locationRelativeToSeoul |
P99945
|
FINISHED |
| Object | south of Seoul |
—
|
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: south of Seoul | Statement: [Battle of Osan, locationRelativeToSeoul, south of Seoul]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationRelativeToSeoul Context triple: [Battle of Osan, locationRelativeToSeoul, south of Seoul]
-
A.
directionFromSeoul
chosen
Indicates the cardinal or relative compass direction in which an entity is located when measured from Seoul.
-
B.
distanceToSeoul
Indicates the measured or estimated spatial distance between a given entity’s location and the city of Seoul.
-
C.
distanceFromApia
Indicates the measured distance between a given location and Apia.
-
D.
distanceFromGwangju
Indicates the spatial distance between a given location and the city of Gwangju.
-
E.
distanceFromJeju
Indicates the spatial distance between a given location or entity and Jeju.
- 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_69f3491213b88190a57094d8697a7455 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a0245e917748190bf0a65db538aa66f |
completed | May 11, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_6a023f7cf7148190af5c2ea501511145 |
completed | May 11, 2026, 8:43 p.m. |
Created at: May 1, 2026, 12:46 a.m.