Triple
T37044713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lakagígar area |
E916873
|
entity |
| Predicate | volcanicSystemLength |
P186938
|
FINISHED |
| Object | approximately 25 kilometres |
—
|
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: approximately 25 kilometres | Statement: [Lakagígar area, volcanicSystemLength, approximately 25 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: volcanicSystemLength Context triple: [Lakagígar area, volcanicSystemLength, approximately 25 kilometres]
-
A.
volcanicComplexDiameter
Indicates the measured diameter or overall lateral extent of a volcanic complex.
-
B.
isPartOfVolcanicSystem
Indicates that one entity belongs to, or is a component within, a larger volcanic system or complex.
-
C.
eruptiveCentersCount
Indicates the number of distinct eruptive centers involved or present in a given volcanic or geological context.
-
D.
volcanoRank
Indicates the relative position or classification of a volcano within an ordered ranking system, such as by size, activity, or hazard level.
-
E.
volcanoNumber
Indicates that an entity is assigned a specific identifying number within a system or catalog of volcanoes.
- F. None of above. chosen
Provenance (4 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.