Triple
T26301754
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cumbre Vieja crest trail |
E661576
|
entity |
| Predicate | approximateType |
P151480
|
FINISHED |
| Object | ridge trail |
—
|
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: ridge trail | Statement: [Cumbre Vieja crest trail, approximateType, ridge trail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateType Context triple: [Cumbre Vieja crest trail, approximateType, ridge trail]
-
A.
approximationType
Indicates the specific method or scheme used to approximate a value, function, or relationship in a given context.
-
B.
hasApproximateType
chosen
Indicates that an entity is associated with a type that is similar or close to, but not exactly, a specified type.
-
C.
approximateDropType
Indicates that one entity represents an estimated or inferred type or category of drop associated with another entity.
-
D.
approximates
Indicates that one entity is close to, but not exactly equal to, the value, form, or behavior of another entity.
-
E.
approximationClass
Indicates a relationship where one entity is classified as an approximation or approximate representation of another.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 26, 2026, 10:16 p.m.