Triple
T3257834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kagoshima Branch of Fukuoka High Court |
E68338
|
entity |
| Predicate | hasBranchStatus |
P12717
|
FINISHED |
| Object | regional branch of Fukuoka High Court |
—
|
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: regional branch of Fukuoka High Court | Statement: [Kagoshima Branch of Fukuoka High Court, hasBranchStatus, regional branch of Fukuoka High Court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchStatus Context triple: [Kagoshima Branch of Fukuoka High Court, hasBranchStatus, regional branch of Fukuoka High Court]
-
A.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
B.
isOnBranch
Indicates that one entity is physically positioned atop or supported by a branch of another entity.
-
C.
hasStatusLabel
chosen
Indicates that an entity is associated with a specific status expressed as a human-readable label.
-
D.
hasReleaseBranch
Indicates that an entity is associated with a specific release branch, typically representing a stabilized version line in a version control or release management system.
-
E.
hasSummaryBranches
Indicates that an entity includes or is associated with summarized versions or high-level branches derived from more detailed components or structures.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaf6a46448190a7fa0ca83fa096f8 |
completed | March 8, 2026, 5:18 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:09 p.m.