Triple
T13706103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilgrim City of Naga |
E328644
|
entity |
| Predicate | hasTypeOfPilgrimage |
P74747
|
FINISHED |
| Object | Marian pilgrimage |
—
|
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: Marian pilgrimage | Statement: [Pilgrim City of Naga, hasTypeOfPilgrimage, Marian pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfPilgrimage Context triple: [Pilgrim City of Naga, hasTypeOfPilgrimage, Marian pilgrimage]
-
A.
hasPilgrimageType
chosen
Indicates that an entity is associated with a specific type or category of pilgrimage.
-
B.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
C.
hasPilgrimageActivity
Indicates that an entity engages in, organizes, or is associated with a religious pilgrimage activity.
-
D.
hasPilgrimagePeak
Indicates that a place or route is associated with a specific peak that serves as a destination or focal point for religious or spiritual pilgrimage.
-
E.
hasPilgrims
Indicates that an entity is associated with or contains pilgrims, typically as visitors, members, or participants in a pilgrimage.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dcad17732c8190bbd0d73107711c99 |
completed | April 13, 2026, 8:45 a.m. |
| PD | Predicate disambiguation | batch_69dbbe92d77c81908e0244cffb7f78c5 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.