Triple
T33979342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camino Francés |
E871230
|
entity |
| Predicate | destinationShrine |
P27875
|
FINISHED |
| Object | Cathedral of Santiago de Compostela |
—
|
NE NERFINISHED |
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: Cathedral of Santiago de Compostela | Statement: [Camino Francés, destinationShrine, Cathedral of Santiago de Compostela]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: destinationShrine Context triple: [Camino Francés, destinationShrine, Cathedral of Santiago de Compostela]
-
A.
possibleShrineLocation
Indicates that a location is suitable or designated as a potential site where a shrine could be placed or constructed.
-
B.
hasNearbyShrine
Indicates that one entity is located close to or in the vicinity of a shrine associated with another entity.
-
C.
containsShrine
Indicates that one entity includes or has within its boundaries a shrine associated with it.
-
D.
majorShrineLocation
Indicates that a major religious shrine is located at or associated with a particular place or geographic location.
-
E.
associatedShrine
chosen
Indicates that there is a specific shrine linked or connected to the given entity, typically as its dedicated or related place of worship or reverence.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:50 a.m.