Triple
T7520828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yongzhou |
E177762
|
entity |
| Predicate | hasProvinceCapitalDistanceRelation |
P10889
|
FINISHED |
| Object | south of Changsha |
—
|
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 Changsha | Statement: [Yongzhou, hasProvinceCapitalDistanceRelation, south of Changsha]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProvinceCapitalDistanceRelation Context triple: [Yongzhou, hasProvinceCapitalDistanceRelation, south of Changsha]
-
A.
adjacentToProvinceCapital
Indicates that a location is directly next to or bordering the capital city of a province.
-
B.
hasCountryCapitalOfProvince
Indicates that a country has a specific city that serves as the capital of one of its provinces.
-
C.
distanceFromCapital
chosen
Indicates the measured distance between a given location and the capital city of its corresponding region or country.
-
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.
prefectureCapitalDistance
Indicates the distance between a prefecture and its designated capital city.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c2ad6c8190b822c0a5b80e7829 |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
Created at: March 27, 2026, 3:46 p.m.