Triple
T16728598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saichō |
E406526
|
entity |
| Predicate | requestedFromCourt |
P124400
|
FINISHED |
| Object | authorization for Mahayana ordination platform |
—
|
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: authorization for Mahayana ordination platform | Statement: [Saichō, requestedFromCourt, authorization for Mahayana ordination platform]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requestedFromCourt Context triple: [Saichō, requestedFromCourt, authorization for Mahayana ordination platform]
-
A.
courtOrdered
Indicates that an action, condition, or relationship exists because it has been formally mandated or imposed by a court order.
-
B.
broughtToCourtBy
Indicates that a person or entity is taken to court or legally prosecuted by another party.
-
C.
confirmedToCourtOn
Indicates that an entity has formally provided confirmation or testimony to a court regarding another entity or matter.
-
D.
originatedInCourt
Indicates that a legal case, decision, or proceeding began or was first filed in a specified court.
-
E.
affectedCourt
Indicates that a particular court is impacted or influenced by a specified action, decision, or legal matter.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e38749baa48190892b2e2b978f6eb6 |
completed | April 18, 2026, 1:29 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326b9e84881909a9166e65bd850d6 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:20 a.m.