Triple
T32392858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Galeras Volcano |
E827721
|
entity |
| Predicate | knownSincePrehistoricTimes |
P179536
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Galeras Volcano, knownSincePrehistoricTimes, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownSincePrehistoricTimes Context triple: [Galeras Volcano, knownSincePrehistoricTimes, true]
-
A.
knownByAncientCivilization
Indicates that something was recognized, documented, or understood by an ancient civilization.
-
B.
inhabitedSince
Indicates that a place has been continuously or initially occupied or lived in by someone or something starting from a specified time.
-
C.
historicPresence
Indicates that an entity existed, was active, or had a notable presence in a particular place or context during a past time period.
-
D.
knownFromFossils
Indicates that the existence or occurrence of something is inferred or established based on fossil evidence.
-
E.
earliestKnownAncestor
Indicates that one entity is the most distant (oldest) known ancestor in the lineage of another entity.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 12:52 a.m.