Triple
T6226686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Thuy District |
E139249
|
entity |
| Predicate | hasProvinceCapitalDistance |
P10889
|
FINISHED |
| Object | south of Dong Hoi |
—
|
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 Dong Hoi | Statement: [Le Thuy District, hasProvinceCapitalDistance, south of Dong Hoi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceCapitalDistance Context triple: [Le Thuy District, hasProvinceCapitalDistance, south of Dong Hoi]
-
A.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
B.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
-
C.
stateCapitalProximity
Indicates the spatial closeness or distance between a state’s capital city and another specified location.
-
D.
capitalOfProvinceNearby
Indicates that a city serves as the capital of a province that is geographically close to a specified reference location or area.
-
E.
isProvincialCapital
Indicates that a location serves as the administrative capital of a province within a country or region.
- 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_69c008afd3148190b71e9eaa60420dd1 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062d5403081908effc8330bda3f0a |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055ffdf54819086d987d646e44ff5 |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:22 p.m.