Triple
T31760726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | City of Jaca |
E810672
|
entity |
| Predicate | hasPilgrimageConnection |
P174115
|
FINISHED |
| Object | Way of St. James |
—
|
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: Way of St. James | Statement: [City of Jaca, hasPilgrimageConnection, Way of St. James]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageConnection Context triple: [City of Jaca, hasPilgrimageConnection, Way of St. James]
-
A.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
B.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
C.
hasPilgrimageObject
Indicates that an entity has a specific object or site that serves as the focus or destination of a pilgrimage associated with it.
-
D.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
-
E.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
- F. None of above. chosen
Provenance (4 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: April 30, 2026, 11:30 p.m.