Triple
T17751713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roraima Tepui |
E443127
|
entity |
| Predicate | hasSummitEcosystem |
P60385
|
FINISHED |
| Object | island-like sky island ecosystem |
—
|
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: island-like sky island ecosystem | Statement: [Roraima Tepui, hasSummitEcosystem, island-like sky island ecosystem]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitEcosystem Context triple: [Roraima Tepui, hasSummitEcosystem, island-like sky island ecosystem]
-
A.
hasSummitFeature
Indicates that a summit (or peak) possesses a particular characteristic, attribute, or notable feature.
-
B.
summitEnvironment
chosen
Indicates the environmental conditions or context present at the summit of a mountain or peak.
-
C.
hasSummitUse
Indicates that something is designated for use specifically at or on a summit (e.g., the top of a mountain or peak).
-
D.
hasSummitVariant
Indicates that an entity has a specific summit-related version or variant associated with it.
-
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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4841b3ccc8190b3241b3e0fa4b2e8 |
completed | April 19, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69e3cde9dc288190af0e2198487f2051 |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:10 a.m.