Triple
T36813718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nakhon Sawan |
E909666
|
entity |
| Predicate | directionFromBangkok |
P196726
|
FINISHED |
| Object | north |
—
|
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: north | Statement: [Nakhon Sawan, directionFromBangkok, north]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directionFromBangkok Context triple: [Nakhon Sawan, directionFromBangkok, north]
-
A.
distanceFromBangkok
Indicates the spatial distance between a given location and the city of Bangkok.
-
B.
directionFromYangon
Indicates the cardinal or relative compass direction in which one location lies from Yangon.
-
C.
distanceFromThonBuriStation_km
Indicates the distance, measured in kilometers, between a given entity and Thon Buri Station.
-
D.
positionRelativeToPattaya
Indicates the spatial or directional relationship of an entity’s location with respect to Pattaya.
-
E.
directionFromTehran
Indicates the cardinal or relative compass direction in which one entity is located from Tehran.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fe629b4fa481908467c7c41b77f0c6 |
completed | May 8, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69fe61bb260c819083f9378a3a06ca47 |
completed | May 8, 2026, 10:20 p.m. |
| PDg | Predicate description generation | batch_69fe629a8d4c8190b4aa4dee39efc0a6 |
completed | May 8, 2026, 10:24 p.m. |
Created at: May 3, 2026, 4:13 p.m.