Triple
T25763297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 洮河 |
E648803
|
entity |
| Predicate | 所在地形区 |
P110443
|
FINISHED |
| Object | 青藏高原东缘 |
—
|
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: 青藏高原东缘 | Statement: [洮河, 所在地形区, 青藏高原东缘]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 所在地形区 Context triple: [洮河, 所在地形区, 青藏高原东缘]
-
A.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
B.
associatedTopography
Indicates a relationship where one entity is linked or connected to a particular topographical feature or terrain.
-
C.
naturalRegionOf
chosen
Indicates that one entity is the natural geographic region or area in which the other entity is located or to which it belongs.
-
D.
physiographicDivisionOf
Indicates that one geographic area is a sub-region or component within the larger physiographic division of another area.
-
E.
topographyBasedOn
Indicates that the topographical characteristics of one entity are derived from, determined by, or modeled using the topography of 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fdf12528819093c47b3af6b865ef |
completed | May 2, 2026, 1:36 p.m. |
| PD | Predicate disambiguation | batch_69f4a0fed15881909b789251fe5d8d45 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 22, 2026, 5:07 a.m.