Triple
T34687378
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lautaro volcano |
E890788
|
entity |
| Predicate | iceCap |
P47165
|
FINISHED |
| Object | Southern Patagonian Ice Field |
—
|
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: Southern Patagonian Ice Field | Statement: [Lautaro volcano, iceCap, Southern Patagonian Ice Field]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iceCap Context triple: [Lautaro volcano, iceCap, Southern Patagonian Ice Field]
-
A.
iceClass
Indicates a classification relationship specifying the level or category of ice-strengthening or ice-navigation capability assigned to a vessel or structure.
-
B.
iceFeature
chosen
Indicates a relationship where a geographic or environmental feature is composed of, covered by, or characterized by ice.
-
C.
iceStrengthened
Indicates that an entity has been made stronger, reinforced, or enhanced through the application or influence of ice.
-
D.
iceCapability
Indicates that an entity has the ability or functional capacity to produce, manage, or utilize ice.
-
E.
iceManagement
Indicates the management, control, or mitigation of ice accumulation or ice-related conditions on or around an entity.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7234f54588190bc19b9cb97244416 |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 2:05 a.m.