Triple
T30625187
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tendai |
E779555
|
entity |
| Predicate | hasOrdinationSystem |
P192494
|
FINISHED |
| Object | Mahāyāna ordination platform at Mount Hiei |
—
|
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: Mahāyāna ordination platform at Mount Hiei | Statement: [Tendai, hasOrdinationSystem, Mahāyāna ordination platform at Mount Hiei]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrdinationSystem Context triple: [Tendai, hasOrdinationSystem, Mahāyāna ordination platform at Mount Hiei]
-
A.
isOrdained
Indicates that an entity has been formally conferred religious or clerical authority through an official ordination process.
-
B.
wasOrdainedAs
Indicates that an entity was formally appointed or consecrated into an official religious or ceremonial role.
-
C.
hasClergyOrder
Indicates that an entity is associated with, or belongs to, a specific religious or clerical order.
-
D.
ordainedIn
Indicates that an individual was formally appointed or consecrated to a religious office or role at a specific place or within a particular institution.
-
E.
allowedOrdinationOf
Indicates that one entity permits or authorizes the formal religious ordination of another entity.
- 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_69f224a431548190a44ad9d088dbf91f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
| PDg | Predicate description generation | batch_69fd0d0aebac8190868a7714ddb4f1fd |
completed | May 7, 2026, 10:07 p.m. |
Created at: April 29, 2026, 8:27 p.m.