Triple
T26516054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divina Pastora Basilica |
E669815
|
entity |
| Predicate | hasProcessionStartingPoint |
P150944
|
FINISHED |
| Object | image of the Divina Pastora |
—
|
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: image of the Divina Pastora | Statement: [Divina Pastora Basilica, hasProcessionStartingPoint, image of the Divina Pastora]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProcessionStartingPoint Context triple: [Divina Pastora Basilica, hasProcessionStartingPoint, image of the Divina Pastora]
-
A.
processionStartingPoint
Indicates the location or entity where a procession begins or is initiated.
-
B.
hasProcessionFrom
chosen
Indicates that a procession, ceremony, or formal movement originates from or starts at a specified source location or entity.
-
C.
hasProcessionDuring
Indicates that a procession or ceremonial march takes place during a specified time period or event.
-
D.
locationOfProcessions
Indicates the place where processions occur or are held.
-
E.
processionRouteEndsAt
Indicates that the endpoint or final destination of a procession’s route is a specified location.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 27, 2026, 1:23 a.m.