Triple
T5875861
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auyán-tepui |
E130622
|
entity |
| Predicate | hasSummitVegetation |
P8666
|
FINISHED |
| Object | shrubs and tepui-adapted plants |
—
|
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: shrubs and tepui-adapted plants | Statement: [Auyán-tepui, hasSummitVegetation, shrubs and tepui-adapted plants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitVegetation Context triple: [Auyán-tepui, hasSummitVegetation, shrubs and tepui-adapted plants]
-
A.
hasSummitArea
Indicates that an entity has a specific area or surface extent associated with its summit or highest point.
-
B.
hasSummitFeature
chosen
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
C.
hasSummit
Indicates that one entity possesses, features, or includes a summit or highest point as part of its structure or characteristics.
-
D.
hasSummitOnSideOf
Indicates that the summit or highest point of one geographic feature is located on the side of another feature.
-
E.
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).
- 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_69c0085523688190bfd487479ce819e6 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0432fea5881909f5c291dd8db6105 |
completed | March 22, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69c033499ca08190bd26cee5b03f6306 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 3:57 p.m.