Triple

T1317877
Position Surface form Disambiguated ID Type / Status
Subject Division II E28146 entity
Predicate promotionSystem P8176 FINISHED
Object top team promoted to higher division 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: top team promoted to higher division | Statement: [Division II, promotionSystem, top team promoted to higher division]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: promotionSystem
Context triple: [Division II, promotionSystem, top team promoted to higher division]
  • A. promotionFrom
    Indicates that an entity has been elevated in position, rank, or status from a specified prior role or level.
  • B. promotionManager
    Indicates that one entity serves as the manager responsible for overseeing or administering the promotion of another entity.
  • C. promotionTo chosen
    Indicates that one entity is elevated or advanced to a higher rank, position, or status relative to another entity or context.
  • D. promotionBetween
    Indicates a relationship where one entity advances or elevates another entity’s status, rank, or visibility relative to a previous state.
  • E. promotionGimmick
    Indicates a relationship where something is used as a special tactic or device to attract attention or boost interest in a promotion.
  • 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_69a498532c3481909223b74af2e578df completed March 1, 2026, 7:49 p.m.
NER Named-entity recognition batch_69a4c176c89881909e9dc0e34f12f056 completed March 1, 2026, 10:45 p.m.
PD Predicate disambiguation batch_69a4beebcb348190964bd7215811942c completed March 1, 2026, 10:34 p.m.
Created at: March 1, 2026, 7:55 p.m.