Triple
T31560922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sarria |
E805259
|
entity |
| Predicate | roleOnCaminoDeSantiago |
P38487
|
FINISHED |
| Object | major starting point |
—
|
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: major starting point | Statement: [Sarria, roleOnCaminoDeSantiago, major starting point]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOnCaminoDeSantiago Context triple: [Sarria, roleOnCaminoDeSantiago, major starting point]
-
A.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
B.
followedOnPilgrimageBy
Indicates that one entity was accompanied or succeeded by another entity during a pilgrimage journey.
-
C.
pilgrimageParticipants
Indicates that certain individuals take part in or accompany a religious pilgrimage.
-
D.
pilgrimageRouteTo
chosen
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
E.
pilgrimageSince
Indicates that an entity has been engaged in or committed to a pilgrimage starting from a specified point in time.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 30, 2026, 10:15 p.m.