Triple
T14340850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 10: Kirihataji |
E355595
|
entity |
| Predicate | pilgrimageStopNumber |
P113873
|
FINISHED |
| Object | 10 |
—
|
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: 10 | Statement: [Temple 10: Kirihataji, pilgrimageStopNumber, 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageStopNumber Context triple: [Temple 10: Kirihataji, pilgrimageStopNumber, 10]
-
A.
tourStopOf
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
-
B.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
C.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
D.
stationNumber
Indicates the specific station identifier or code assigned to an entity within a system or network.
-
E.
pilgrimageRouteTo
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
- 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_69d8278fa2108190bc0d0e7939c1eb03 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e87febc8190a63c668cbd0fd713 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
| PDg | Predicate description generation | batch_69de2e8a40e4819080240c874da1842c |
completed | April 14, 2026, 12:09 p.m. |
Created at: April 10, 2026, 1:14 a.m.