Triple
T2966543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Icefield |
E80177
|
entity |
| Predicate | hasLocationRelativeTo |
P7317
|
FINISHED |
| Object | north of the summit crater of Kibo |
—
|
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: north of the summit crater of Kibo | Statement: [Northern Icefield, hasLocationRelativeTo, north of the summit crater of Kibo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLocationRelativeTo Context triple: [Northern Icefield, hasLocationRelativeTo, north of the summit crater of Kibo]
-
A.
hasRelativeLocation
chosen
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
positionedRelativeTo
Indicates that one entity’s spatial location is defined or described in relation to the position of another entity.
-
C.
hasLocationComponent
Indicates that something includes, is associated with, or is composed of a specific location-related part or element.
-
D.
refersToLocation
Indicates that one entity designates, points to, or identifies a specific location associated with it.
-
E.
hasCanonicalLocation
Indicates that an entity is associated with its primary, standard, or officially recognized location.
- 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_69ad8b1341848190bd19dbf46892887d |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad996e93788190ba9883714d4dfa0c |
completed | March 8, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69ad960e71f8819088179d11248c6ed0 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:58 p.m.