Triple
T9119137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yamaloka |
E218799
|
entity |
| Predicate | hasJudicialAspect |
P10526
|
FINISHED |
| Object | court of Yama |
—
|
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: court of Yama | Statement: [Yamaloka, hasJudicialAspect, court of Yama]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJudicialAspect Context triple: [Yamaloka, hasJudicialAspect, court of Yama]
-
A.
hasJudiciary
chosen
Indicates that an entity possesses, is served by, or is under the authority of a judicial body or legal court system.
-
B.
hasPartInJurisprudence
Indicates that one legal concept, rule, or component forms a constituent part of another within the domain of jurisprudence.
-
C.
judgmentInvolves
Indicates that a particular judgment, decision, or legal ruling includes, concerns, or pertains to a specified entity or matter.
-
D.
hadJudicialFunction
Indicates that an entity exercised or was assigned an official judicial role, authority, or responsibility in relation to another entity or context.
-
E.
hasJustice
Indicates that an entity possesses, upholds, or embodies justice in its actions, qualities, or governing principles.
- 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_69ca83dddd548190983b96c664f7f367 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8a7c6d48190a015efd17a017ca1 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc66003e3c819091e1e42c9cf7c781 |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:17 p.m.