Triple
T9882390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pico Basilé |
E180841
|
entity |
| Predicate | hasSummitInstallations |
P27847
|
FINISHED |
| Object | telecommunications facilities |
—
|
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: telecommunications facilities | Statement: [Pico Basilé, hasSummitInstallations, telecommunications facilities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSummitInstallations Context triple: [Pico Basilé, hasSummitInstallations, telecommunications facilities]
-
A.
hasSummitFacility
chosen
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).
-
B.
hasSummitFeature
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.
hasSummitUse
Indicates that something is designated for use specifically at or on a summit (e.g., the top of a mountain or peak).
-
E.
hasSummitTrail
Indicates that there exists a trail or route leading to the summit or highest point of a geographic feature.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb418417c8190b00dea8916a2e102 |
completed | April 2, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.