Triple
T34688036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cordillera Real (Ecuador) |
E890803
|
entity |
| Predicate | highestPointsType |
P18615
|
FINISHED |
| Object | volcanic summits |
—
|
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: volcanic summits | Statement: [Cordillera Real (Ecuador), highestPointsType, volcanic summits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestPointsType Context triple: [Cordillera Real (Ecuador), highestPointsType, volcanic summits]
-
A.
highestPointsCategory
Indicates the category in which an entity has achieved the greatest number of points compared to all other categories.
-
B.
highestPointsForm
Indicates that a given form or configuration achieves the greatest number of points compared to all other relevant forms.
-
C.
hasHighestPoints
Indicates that the subject entity possesses the greatest number of points compared to all relevant others in the given context.
-
D.
hasHighestPointType
chosen
Indicates that the highest point of an entity is of a specified type or category.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69fd4f39b5008190b83b3227ce22c509 |
completed | May 8, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69fd4df17c548190a4e2a6fea70f7e10 |
completed | May 8, 2026, 2:44 a.m. |
Created at: May 1, 2026, 2:05 a.m.