Triple
T24277491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ko Muk |
E605449
|
entity |
| Predicate | nearestMainlandProvince |
P155635
|
FINISHED |
| Object | Trang Province |
—
|
NE NERFINISHED |
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: Trang Province | Statement: [Ko Muk, nearestMainlandProvince, Trang Province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearestMainlandProvince Context triple: [Ko Muk, nearestMainlandProvince, Trang Province]
-
A.
nearestMainlandState
Indicates the relationship where a given location is associated with the closest U.S. mainland state in terms of geographic proximity.
-
B.
nearestMainlandPoint
Indicates the relationship where a location is associated with the closest point on the mainland to that location.
-
C.
nearestStateOrTerritory
Indicates that one location is the closest state or territory to another location, typically in terms of geographic distance.
-
D.
nearProvince
Indicates that one province is geographically close to or bordering another province.
-
E.
nearbyCountryProvince
Indicates that a province is geographically close to, or shares a border with, a specified country.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d60a454819093b46556966640ab |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:07 a.m.