Triple
T12287284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cilindro de Marboré |
E292861
|
entity |
| Predicate | isPopularThreeThousanderList |
P20205
|
FINISHED |
| Object | Pyrenean three-thousanders |
—
|
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: Pyrenean three-thousanders | Statement: [Cilindro de Marboré, isPopularThreeThousanderList, Pyrenean three-thousanders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularThreeThousanderList Context triple: [Cilindro de Marboré, isPopularThreeThousanderList, Pyrenean three-thousanders]
-
A.
isOnlyFourThousanderOf
Indicates that one entity is the sole mountain in a given region or context whose elevation exceeds four thousand meters.
-
B.
hasPeakOver3000m
Indicates that the related geographic feature has at least one peak whose elevation exceeds 3000 meters above sea level.
-
C.
hasTouristPopularity
chosen
Indicates that a place or attraction is recognized as being popular or frequently visited by tourists.
-
D.
oneOfThreePeaksOf
Indicates that the subject is one of the three principal peaks associated with the object.
-
E.
isPopularWith
Indicates that one entity is well-liked, favored, or widely accepted by another entity or group.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d9261e1570819084bb4fdb44aa6aea |
completed | April 10, 2026, 4:32 p.m. |
| PD | Predicate disambiguation | batch_69d91c4d9a9c8190aeb7beaf9792d8f0 |
completed | April 10, 2026, 3:50 p.m. |
Created at: April 8, 2026, 9:52 p.m.