Triple
T14930839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple 87: Nagaoji |
E372258
|
entity |
| Predicate | pilgrimageSequencePosition |
P113873
|
FINISHED |
| Object | eighty-seventh temple |
—
|
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: eighty-seventh temple | Statement: [Temple 87: Nagaoji, pilgrimageSequencePosition, eighty-seventh temple]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilgrimageSequencePosition Context triple: [Temple 87: Nagaoji, pilgrimageSequencePosition, eighty-seventh temple]
-
A.
pilgrimageRoutePosition
Indicates the relative location or stage of an entity along a designated pilgrimage route.
-
B.
pilgrimageNumber
Indicates the number or count associated with a particular pilgrimage event or journey.
-
C.
precedesInPilgrimage
Indicates that one entity undertakes or occurs in the pilgrimage before another entity in an ordered sequence.
-
D.
pilgrimageStopNumber
chosen
Indicates the ordinal position of a specific stop or location within a defined pilgrimage route or sequence.
-
E.
hasPilgrimageNumber
Indicates that an entity is associated with a specific pilgrimage identification number, typically used to track or distinguish individual pilgrimages or pilgrims.
- 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_69d85cc9da0c81908d583ca3f63a3908 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded64550dc8190ba44120df00ba498 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:36 a.m.