Triple
T14964621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 65: Sankakuji |
E373157
|
entity |
| Predicate | hasNumberWithinPilgrimage |
P113863
|
FINISHED |
| Object | 65 |
—
|
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: 65 | Statement: [Temple 65: Sankakuji, hasNumberWithinPilgrimage, 65]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNumberWithinPilgrimage Context triple: [Temple 65: Sankakuji, hasNumberWithinPilgrimage, 65]
-
A.
hasPilgrimageNumber
chosen
Indicates that an entity is associated with a specific pilgrimage identification number, typically used to track or distinguish individual pilgrimages or pilgrims.
-
B.
pilgrimageNumber
Indicates the number or count associated with a particular pilgrimage event or journey.
-
C.
hasPilgrimageFrom
Indicates that a pilgrimage originates from or is undertaken starting at a specified location or source.
-
D.
hasPilgrimageRegion
Indicates that an entity is associated with a specific region that serves as the destination or location for its pilgrimage activities.
-
E.
hasPilgrimageStamp
Indicates that an entity possesses or has received a stamp documenting participation 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_69d85ccbbcd48190acb56e7cf104d8ad |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded6d0487c8190b7754af8c5014b37 |
completed | April 15, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69de9a5d995881909e33658f5aea5582 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:45 a.m.