Triple
T1155877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Bench |
E23780
|
entity |
| Predicate | partOfBranch |
P22486
|
FINISHED |
| Object | judicial branch of Japan |
—
|
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: judicial branch of Japan | Statement: [Grand Bench, partOfBranch, judicial branch of Japan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfBranch Context triple: [Grand Bench, partOfBranch, judicial branch of Japan]
-
A.
isPartOfBranchTypically
chosen
Indicates that something is typically a component or subdivision within a larger branch.
-
B.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
C.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
D.
involvedBranch
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
E.
isUniqueBranchOf
Indicates that one branch is the sole or distinct sub-branch associated with a particular parent entity or structure.
- 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_69a493f0d32c8190ac74bad3c87f2641 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc912300819084c9c69783055a70 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb50d19c81908a98dbbb04a8906f |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.