Triple
T7519071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nevado del Huila |
E177719
|
entity |
| Predicate | dormantForCenturiesBeforeRecentActivity |
P77437
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Nevado del Huila, dormantForCenturiesBeforeRecentActivity, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dormantForCenturiesBeforeRecentActivity Context triple: [Nevado del Huila, dormantForCenturiesBeforeRecentActivity, yes]
-
A.
activeUntilCentury
Indicates that an entity remains active or in effect up to and including a specified century.
-
B.
usedSinceCentury
Indicates that something has been in use starting from a specified century.
-
C.
existsSinceCentury
Indicates that an entity has existed or been in effect since a specified century.
-
D.
hasLastEruptionCentury
Indicates the century during which the most recent eruption of a volcano (or eruptive feature) occurred.
-
E.
hasArchaeologicalExcavationsSince
Indicates that archaeological excavations have been conducted at an entity starting from a specified point in time and continuing since then.
- 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_69c69f2891148190a484f3b8222c6f1b |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f5f850c081909e697219071293fc |
completed | March 27, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d44e9481909813e073b194f6f4 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f574d8a8819095749518dad13791 |
completed | March 27, 2026, 9:24 p.m. |
Created at: March 27, 2026, 3:46 p.m.