Triple
T24829810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Macbeth Glacier |
E621304
|
entity |
| Predicate | geologicFeatureType |
P130093
|
FINISHED |
| Object | valley glacier |
—
|
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: valley glacier | Statement: [Macbeth Glacier, geologicFeatureType, valley glacier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: geologicFeatureType Context triple: [Macbeth Glacier, geologicFeatureType, valley glacier]
-
A.
geologicType
Indicates the specific geological classification or category assigned to a rock, soil, or earth material unit.
-
B.
geologicalFormation
Indicates that one entity is a geological structure or feature that characterizes or composes the physical makeup of another entity.
-
C.
isTectonicFeature
Indicates that something is a geological structure or formation resulting from tectonic processes or plate movements.
-
D.
hasTypeOfTectonicFeature
Indicates that one entity is characterized by or classified as a specific type of tectonic feature (such as a fault, plate boundary, or rift).
-
E.
geomorphicType
chosen
Indicates the classification of a geographic feature based on its landform or geomorphic characteristics.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:14 a.m.