Triple
T24740565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diavolo Glacier |
E618545
|
entity |
| Predicate | hasParentMountainRange |
P76788
|
FINISHED |
| Object | Coast Mountains |
—
|
NE NERFINISHED |
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: Coast Mountains | Statement: [Diavolo Glacier, hasParentMountainRange, Coast Mountains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentMountainRange Context triple: [Diavolo Glacier, hasParentMountainRange, Coast Mountains]
-
A.
parentMountain
Indicates that one mountain is considered the larger or primary "parent" from which another, related "child" mountain is derived or associated.
-
B.
hasMountainRange
Indicates that one entity possesses, contains, or is geographically associated with a specific mountain range.
-
C.
originatesFromMountainRange
Indicates that something has its source or beginning in a specific mountain range.
-
D.
associatedWithMountainRange
chosen
Indicates a relationship where something is connected or related in some way to a specific mountain range.
-
E.
sourceMountainRange
Indicates that a river, stream, or similar feature originates from or has its source in a specified mountain 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_69e2fab8f95c81908bb9e552cf3280c2 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:05 a.m.