Triple
T6246760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qinling Mountains |
E139738
|
entity |
| Predicate | climateBoundaryBetween |
P69296
|
FINISHED |
| Object | humid subtropical climate of southern China |
—
|
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: humid subtropical climate of southern China | Statement: [Qinling Mountains, climateBoundaryBetween, humid subtropical climate of southern China]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: climateBoundaryBetween Context triple: [Qinling Mountains, climateBoundaryBetween, humid subtropical climate of southern China]
-
A.
boundaryBetween
Indicates that something serves as a dividing line or limit separating two distinct regions, areas, or entities.
-
B.
climateAlongBorder
Indicates that two regions share similar or related climatic conditions specifically along their common border.
-
C.
fareBoundaryBetween
Indicates that there is a dividing line or zone where one fare region, zone, or pricing scheme ends and another begins.
-
D.
plateBoundaryBetween
Indicates a geological relationship where a boundary exists between two tectonic plates.
-
E.
boundaryName
Indicates the designated name or label assigned to a specific boundary or border between entities.
- F. None of above. chosen
Provenance (4 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_69c008b1c5088190ae6de2555fc05ad8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0631f511c81908d413320efdce42e |
completed | March 22, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69c056037bf88190a0a3fe7429345d0b |
completed | March 22, 2026, 8:50 p.m. |
| PDg | Predicate description generation | batch_69c056df95ac8190bc5efe050d3af864 |
completed | March 22, 2026, 8:53 p.m. |
Created at: March 22, 2026, 4:23 p.m.