Triple

T186410
Position Surface form Disambiguated ID Type / Status
Subject district courts of Japan E3990 entity
Predicate hasSummaryBranches P6715 FINISHED
Object some summary branches in remote areas 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: some summary branches in remote areas | Statement: [district courts of Japan, hasSummaryBranches, some summary branches in remote areas]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSummaryBranches
Context triple: [district courts of Japan, hasSummaryBranches, some summary branches in remote areas]
  • A. hasMajorBranch
    Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
  • B. usedByBranch
    Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
  • C. hasExtinctBranch
    Indicates that an entity has at least one branch, lineage, or subdivision that no longer exists (is extinct).
  • D. hasMainTrunkLine
    Indicates that an entity is connected to or served by a primary or central trunk line within a network or system.
  • E. branchChecked
    Indicates that a specific branch (such as in version control or a decision tree) has been examined or verified.
  • 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_69a25497e2f08190a040f8c6e1842643 completed Feb. 28, 2026, 2:36 a.m.
NER Named-entity recognition batch_69a2594809288190b3d3b1283e7e0d00 completed Feb. 28, 2026, 2:56 a.m.
PD Predicate disambiguation batch_69a25670feb081908e26a2543ebe7b3a completed Feb. 28, 2026, 2:44 a.m.
PDg Predicate description generation batch_69a257e763d081908c54ad57d8d3060d completed Feb. 28, 2026, 2:50 a.m.
Created at: Feb. 28, 2026, 2:40 a.m.