Triple
T28813302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 北岳 |
E727573
|
entity |
| Predicate | 属する山塊 |
P119151
|
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.
hasMountainGroup
chosen
Indicates that one entity is associated with, belongs to, or is part of a particular group or range of mountains.
-
B.
associatedWithMountainRange
Indicates a relationship where something is connected or related in some way to a specific mountain range.
-
C.
orogenAssociatedWith
Indicates an association between a geological feature or process and a specific orogen (mountain-building event or belt), without specifying the exact nature of that association.
-
D.
mountainRange
Indicates that one entity is a mountain range that the other entity is part of, associated with, or located in.
-
E.
mountainSystem
Indicates a relationship where multiple mountains are grouped together as part of the same connected or coherent mountain system or range.
- 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_69f0319c38948190bca746ad60fd25ba |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f658f163a88190b1dd222eaa0f93ea |
completed | May 2, 2026, 8:05 p.m. |
| PD | Predicate disambiguation | batch_69f65760fd3081908ffe014a5e2bf069 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:31 a.m.