Triple
T2476153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Licancabur |
E55092
|
entity |
| Predicate | summitFeatures |
P8666
|
FINISHED |
| Object | crater about 400 m in diameter |
—
|
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: crater about 400 m in diameter | Statement: [Licancabur, summitFeatures, crater about 400 m in diameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: summitFeatures Context triple: [Licancabur, summitFeatures, crater about 400 m in diameter]
-
A.
hasSummitFeature
chosen
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
B.
summitAccessibleFrom
Indicates that a summit can be reached or accessed starting from a specified location or route.
-
C.
summitAffected
Indicates that a summit, meeting, or high-level event has been influenced, impacted, or altered by a specified factor or circumstance.
-
D.
hasSummitFacility
Indicates that one entity possesses or provides a facility or infrastructure located at the summit of another entity (such as a mountain, hill, or peak).
-
E.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd1eb3be481908fa7c6b8f1c78209 |
completed | March 7, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69abd0b5e3d481909a5cbc4a96edd24f |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:45 p.m.