Triple
T23463742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee of 1300 |
E569049
|
entity |
| Predicate | hasPilgrimagePattern |
P74747
|
FINISHED |
| Object | visits to major Roman basilicas |
—
|
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: visits to major Roman basilicas | Statement: [Jubilee of 1300, hasPilgrimagePattern, visits to major Roman basilicas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimagePattern Context triple: [Jubilee of 1300, hasPilgrimagePattern, visits to major Roman basilicas]
-
A.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
B.
hasPilgrimageType
chosen
Indicates that an entity is associated with a specific type or category of pilgrimage.
-
C.
hasPilgrimageFocus
Indicates that something is centered on, dedicated to, or primarily concerned with religious or spiritual pilgrimage activities or themes.
-
D.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
E.
hasPilgrimageRouteType
Indicates that a pilgrimage route is associated with a specific type or category of pilgrimage path.
- 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_69e2458ebd808190b3298163132cfb0b |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a69f0a54819084c19c248a572253 |
completed | April 29, 2026, 6:35 a.m. |
| PD | Predicate disambiguation | batch_69f06201d33481909b5fd7b92d03e658 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:54 p.m.