Triple

T36270974
Position Surface form Disambiguated ID Type / Status
Subject Super Over E892671 entity
Predicate boundaryCountRuleStatus P185076 FINISHED
Object later removed from ICC playing conditions 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: later removed from ICC playing conditions | Statement: [Super Over, boundaryCountRuleStatus, later removed from ICC playing conditions]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: boundaryCountRuleStatus
Context triple: [Super Over, boundaryCountRuleStatus, later removed from ICC playing conditions]
  • A. boundaryStatus
    Indicates the status or condition of a boundary between entities, such as whether it is defined, active, disputed, or otherwise characterized.
  • B. borderDefinedBetween
    Indicates that a boundary line or border is formally established between two geographic or political entities.
  • C. hasBorderAreaStatus
    Indicates that an entity has a designated status related to being in or associated with a border area.
  • D. boundaryReviewRegion
    Indicates that a specified region is under consideration or subject to evaluation in a boundary review process.
  • E. boundaryMetric
    Indicates a relationship where a quantitative measure is assigned to the boundary or interface between entities, capturing some property (such as distance, similarity, or cost) of that boundary.
  • 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_69f76e488f34819083e254dbe288c27a completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69f7bb1d6b70819091227bd011734d19 completed May 3, 2026, 9:16 p.m.
PD Predicate disambiguation batch_69f7b9a4aad48190a62e41c5e39339d9 completed May 3, 2026, 9:09 p.m.
PDg Predicate description generation batch_69f7ba6c27e081908868a2b50d1d603c completed May 3, 2026, 9:13 p.m.
Created at: May 3, 2026, 4:09 p.m.