Triple
T31976323
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 澜沧江 |
E816457
|
entity |
| Predicate | 在中国境内长度 |
P125267
|
FINISHED |
| Object | 约2160千米 |
—
|
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: 约2160千米 | Statement: [澜沧江, 在中国境内长度, 约2160千米]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在中国境内长度 Context triple: [澜沧江, 在中国境内长度, 约2160千米]
-
A.
lengthInChina
chosen
Indicates that the specified length or distance is measured according to standards, units, or conditions applicable within China.
-
B.
hasMainlandLengthApproxKm
Indicates the approximate length of an entity’s mainland portion, measured in kilometers.
-
C.
hasInternationalBoundaryLengthWithChina
Indicates that there exists a shared land or river border between the subject entity and China, and specifies the length of that international boundary.
-
D.
rankingByLengthInChina
Indicates that entities are ordered or evaluated based on their length within the context of China.
-
E.
includesProvinceOnChinaSide
Indicates that a specified entity encompasses or contains a province located on the Chinese side of a border or boundary.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b344b24881908bf1da55fd9b3a97 |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.