Triple
T5020724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canigou |
E112841
|
entity |
| Predicate | isSacredMountainFor |
P31798
|
FINISHED |
| Object | Catalan culture |
—
|
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: Catalan culture | Statement: [Canigou, isSacredMountainFor, Catalan culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSacredMountainFor Context triple: [Canigou, isSacredMountainFor, Catalan culture]
-
A.
isRockySummitOf
Indicates that one entity is the rocky summit or peak portion of another, typically higher-level, geographic feature.
-
B.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
C.
symbolicMountain
chosen
Indicates that a mountain functions as a symbol or emblem representing some idea, value, or entity.
-
D.
hasPilgrimagePeak
Indicates that a place or route is associated with a specific peak that serves as a destination or focal point for religious or spiritual pilgrimage.
-
E.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
- 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_69bd4435c2f48190be593158cbfcf8a3 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd736399ac8190aa38efc4b4edc6a2 |
completed | March 20, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69bd714ecfe08190b5830cfc1c74fa17 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.