Triple
T34943301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 宝塔山 |
E1007785
|
entity |
| Predicate | 地理类型 |
P41592
|
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.
geographicalNature
Indicates the natural geographic characteristics or physical landscape type associated with a place or region.
-
B.
naturalRegionType
chosen
Indicates the type or category of natural region to which a given area or place belongs.
-
C.
physiographicClassificationBy
Indicates a relationship where an entity is assigned a physiographic category or type according to a specified classifier, method, or authority.
-
D.
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).
-
E.
topographicalCategory
Indicates the type of landform or surface feature that characterizes the physical terrain associated with an 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782c98fa08190870b68de2c1ff26a |
completed | May 3, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69f781020cc4819088c40cb8589504e4 |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.