Triple
T15089200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 34: Tanemaji |
E360368
|
entity |
| Predicate | hasPilgrimageRouteType |
P117261
|
FINISHED |
| Object | circular 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: circular pilgrimage | Statement: [Temple 34: Tanemaji, hasPilgrimageRouteType, circular pilgrimage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPilgrimageRouteType Context triple: [Temple 34: Tanemaji, hasPilgrimageRouteType, circular pilgrimage]
-
A.
hasPilgrimageType
Indicates that an entity is associated with a specific type or category of pilgrimage.
-
B.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
C.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
D.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
E.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec71e8dcc81908badc834b6ccf273 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:04 a.m.