Triple
T32306732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pye |
E825390
|
entity |
| Predicate | distanceFromYangonApproximate |
P203197
|
FINISHED |
| Object | 260 km northwest |
—
|
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: 260 km northwest | Statement: [Pye, distanceFromYangonApproximate, 260 km northwest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceFromYangonApproximate Context triple: [Pye, distanceFromYangonApproximate, 260 km northwest]
-
A.
distanceToYangon_km
chosen
Indicates the physical distance, measured in kilometers, between a given location and Yangon.
-
B.
distanceFromMawlamyine_km
Indicates the distance, measured in kilometers, between a given place or entity and Mawlamyine.
-
C.
distanceFromMandalay
Indicates the measured distance between a given place or entity and the location of Mandalay.
-
D.
directionFromYangon
Indicates the cardinal or relative compass direction in which one location lies from Yangon.
-
E.
approximateDistanceInKilometersFromChiangMai
Indicates the approximate physical distance, measured in kilometers, between a given entity’s location and Chiang Mai.
- 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_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a03544239d4819087b6c232d6804977 |
completed | May 12, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_6a0353d685688190b01df77fc2f62bf2 |
completed | May 12, 2026, 4:22 p.m. |
Created at: May 1, 2026, 12:45 a.m.