Triple
T35877081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Burney |
E1037395
|
entity |
| Predicate | hasTephraLayersIdentifiedIn |
P123824
|
FINISHED |
| Object | Patagonian lakes |
—
|
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: Patagonian lakes | Statement: [Mount Burney, hasTephraLayersIdentifiedIn, Patagonian lakes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTephraLayersIdentifiedIn Context triple: [Mount Burney, hasTephraLayersIdentifiedIn, Patagonian lakes]
-
A.
hasPyroclasticDeposits
Indicates that an entity exhibits or contains accumulations of pyroclastic volcanic material deposited by explosive eruptions.
-
B.
tephraVolume
Indicates the amount of volcanic tephra produced or present, typically expressed as a measurable volume.
-
C.
hasVolcanicProduct
chosen
Indicates that an entity possesses, contains, or is associated with material or products originating from volcanic activity.
-
D.
tephraName
Indicates that one entity is the designated name or label assigned to a specific tephra (volcanic ash or pyroclastic) unit.
-
E.
hasVolcanicAsh
Indicates that there is volcanic ash present on, in, or associated with a specified entity or 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_69f76e1e701c8190a4990d4978ce4fe6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe78e545888190a239af1a84280fa0 |
completed | May 8, 2026, 11:59 p.m. |
| PD | Predicate disambiguation | batch_69fe7842742081908043eb950ed69f92 |
completed | May 8, 2026, 11:56 p.m. |
Created at: May 3, 2026, 4:06 p.m.