Triple

T7983505
Position Surface form Disambiguated ID Type / Status
Subject Regionalliga E185629 entity
Predicate restructuredAsTier P12792 FINISHED
Object 2008 (as fourth tier after creation of 3. Liga) 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: 2008 (as fourth tier after creation of 3. Liga) | Statement: [Regionalliga, restructuredAsTier, 2008 (as fourth tier after creation of 3. Liga)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: restructuredAsTier
Context triple: [Regionalliga, restructuredAsTier, 2008 (as fourth tier after creation of 3. Liga)]
  • A. reorganizedAs
    Indicates that an existing entity has been restructured or reconfigured into a new organizational form or arrangement.
  • B. partOfTier
    Indicates that one entity belongs to, is included within, or forms a component of a specified tier or level in a hierarchical structure.
  • C. thirdTier
    Indicates that an entity occupies a third level or rank within a hierarchical structure or classification.
  • D. reorganizedIn
    Indicates that an entity underwent a structural or organizational change within a specified context, time, or framework.
  • E. hadRankStructureReformedIn chosen
    Indicates that an entity’s rank structure was reorganized, modified, or reformed during a specified time or in a specified context.
  • 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_69ca829a2cfc819083d591d58ec04075 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c2a1aa881909c3cea280dff38f5 completed March 31, 2026, 3:14 a.m.
PD Predicate disambiguation batch_69cb048009a08190b4c577208a9f8f76 completed March 30, 2026, 11:17 p.m.
Created at: March 30, 2026, 5:15 p.m.