Triple
T35725776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 延河 |
E1032607
|
entity |
| Predicate | 地貌区 |
P80940
|
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.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
B.
topographicalCategory
chosen
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an entity.
-
C.
naturalRegionType
Indicates the type or category of natural region to which a given area or place belongs.
-
D.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
-
E.
physiographicSystem
Indicates a relationship where one entity is classified as, or associated with, a particular physiographic system (a distinct large-scale physical landscape or geomorphic 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_69f76e102b5881909e5d63a30a5cecbe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.