Triple

T2568681
Position Surface form Disambiguated ID Type / Status
Subject Midwest League E57612 entity
Predicate hasDivisionStructure P14872 FINISHED
Object divisions 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: divisions | Statement: [Midwest League, hasDivisionStructure, divisions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDivisionStructure
Context triple: [Midwest League, hasDivisionStructure, divisions]
  • A. hasDivisionLevel
    Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
  • B. divisionOrStructure chosen
    Indicates a relationship where one entity is an internal division, department, or structural subunit that is organizationally contained within another entity.
  • C. hasDivisionCode
    Indicates that an entity is associated with a specific division identifier or code within an organizational or classification structure.
  • D. hasOrganizationalStructure
    Indicates that an entity possesses a defined internal arrangement of roles, responsibilities, and relationships that determine how it is organized and operates.
  • E. hasBusinessDivision
    Indicates that an organization includes or is composed of a specific business division as a subordinate unit.
  • 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_69ab4a51410081908501dcf8bad9adc4 completed March 6, 2026, 9:42 p.m.
NER Named-entity recognition batch_69abd36191848190b6255fa9029429bd completed March 7, 2026, 7:27 a.m.
PD Predicate disambiguation batch_69abd0cc8d308190ae7aa32b8f5ae2e5 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:48 p.m.