Triple
T106059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Japan |
E2138
|
entity |
| Predicate | numberOfGrandBenchJustices |
P2279
|
FINISHED |
| Object | 15 |
—
|
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: 15 | Statement: [Supreme Court of Japan, numberOfGrandBenchJustices, 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfGrandBenchJustices Context triple: [Supreme Court of Japan, numberOfGrandBenchJustices, 15]
-
A.
numberOfJudges
chosen
Indicates the total count of judges associated with a particular case, event, or entity.
-
B.
chiefJusticeSinceYear
Indicates that an entity has held the position of chief justice starting from a specified year.
-
C.
chiefJustice
Indicates that one entity serves as the chief justice (the highest-ranking judicial officer) of another entity, such as a court or jurisdiction.
-
D.
hasConcurringJustice
Indicates that a judicial decision is associated with a justice who wrote or joined a concurring opinion.
-
E.
hasDissentingJustice
Indicates that within a judicial decision or ruling, there exists at least one justice who formally disagrees with the majority opinion.
- 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_69a24e0a5b7c81908d52da08c60dabc4 |
completed | Feb. 28, 2026, 2:08 a.m. |
| NER | Named-entity recognition | batch_69a256ec650c8190bee2067e37065527 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563d33788190999d471b486d5603 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:12 a.m.