Triple
T4007315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tendai Buddhism |
E89555
|
entity |
| Predicate | associatedWithMountainAscetics |
P38502
|
FINISHED |
| Object | yamabushi |
—
|
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: yamabushi | Statement: [Tendai Buddhism, associatedWithMountainAscetics, yamabushi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithMountainAscetics Context triple: [Tendai Buddhism, associatedWithMountainAscetics, yamabushi]
-
A.
associatedWithMountain
chosen
Indicates a relationship in which something has a connection, link, or relevance to a mountain.
-
B.
monasteryAffiliation
Indicates a relationship where an entity is formally associated with, belongs to, or is under the authority of a particular monastery.
-
C.
symbolicMountain
Indicates that a mountain functions as a symbol or emblem representing some idea, value, or entity.
-
D.
pilgrimageAssociatedWith
Indicates a relationship where a pilgrimage is connected or related to a particular entity, such as a place, person, event, or religious tradition.
-
E.
nearestSummit
Indicates that one summit is the closest in distance to a given reference point or location compared to all other summits.
- 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_69aed9585e788190bec2d39deba3750f |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:34 p.m.