Triple
T26953187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canary Islands laurel pigeon |
E678827
|
entity |
| Predicate | prefersAltitude |
P130186
|
FINISHED |
| Object | mid-elevation forests |
—
|
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: mid-elevation forests | Statement: [Canary Islands laurel pigeon, prefersAltitude, mid-elevation forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prefersAltitude Context triple: [Canary Islands laurel pigeon, prefersAltitude, mid-elevation forests]
-
A.
elevationPreference
chosen
Indicates a tendency or preference for a certain elevation or altitude relative to other possible elevation levels.
-
B.
meetsAtAltitude
Indicates that two or more entities come together or intersect at a specific vertical height or elevation.
-
C.
locatedAtAltitude
Indicates that an entity exists or is positioned at a specific height above a reference level, typically sea level.
-
D.
hasAltitudeFeature
Indicates that an entity possesses a characteristic or attribute related to its elevation or vertical position above a reference level.
-
E.
extendsFromAltitude
Indicates a relationship where something stretches or reaches outward starting from a specified altitude.
- 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_69eeeb4e75f08190b14fc91ca4a91488 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 6:25 a.m.