Triple
T34952710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navanakorn Industrial Estate |
E1008042
|
entity |
| Predicate | distanceRelationTo |
P53174
|
FINISHED |
| Object | just north of Bangkok |
—
|
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: just north of Bangkok | Statement: [Navanakorn Industrial Estate, distanceRelationTo, just north of Bangkok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: distanceRelationTo Context triple: [Navanakorn Industrial Estate, distanceRelationTo, just north of Bangkok]
-
A.
distancedFrom
Indicates that one entity is physically or metaphorically kept at a certain distance or separation from another entity.
-
B.
proximityToLandmark
chosen
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
C.
roadDistanceRelation
Indicates a relationship specifying the distance between two locations as measured along a road or road network.
-
D.
distancesFrom
Indicates the measured spatial separation between one entity and one or more other entities.
-
E.
nearbyTo
Indicates that one entity is located close in distance or position to another entity.
- 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_69f76dc5d4308190b77553ee07b1ede6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379ff1ba081908eda86acefcf69fb |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.