Triple
T9689175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hozomon Gate |
E234493
|
entity |
| Predicate | isPartOfPilgrimageRoute |
P38487
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Hozomon Gate, isPartOfPilgrimageRoute, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfPilgrimageRoute Context triple: [Hozomon Gate, isPartOfPilgrimageRoute, yes]
-
A.
isPilgrimageDestination
Indicates that a place serves as a destination specifically visited by people undertaking a religious or spiritual pilgrimage.
-
B.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
C.
pilgrimageRouteTo
chosen
Indicates a route or path that is traditionally used or designated for making a religious or spiritual pilgrimage to a particular destination.
-
D.
isPlaceOfPilgrimageFor
Indicates that a location serves as a destination for religious or spiritual pilgrimage for a person or group.
-
E.
containsPilgrimageTown
Indicates that a place or region includes within its boundaries a town that serves as a destination or center for religious 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_69ca84ca73208190957a900c8543bdcc |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9d019d40819095059a4d6167900a |
completed | April 1, 2026, 10:32 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b840f081909f66bf0b66d17d9b |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:17 p.m.