Triple

T29710336
Position Surface form Disambiguated ID Type / Status
Subject FIFA World Cup group tiebreaking criteria E751760 entity
Predicate rankingOrderThen P37518 FINISHED
Object overall goals scored 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: overall goals scored | Statement: [FIFA World Cup group tiebreaking criteria, rankingOrderThen, overall goals scored]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rankingOrderThen
Context triple: [FIFA World Cup group tiebreaking criteria, rankingOrderThen, overall goals scored]
  • A. rankingOrderStartsWith
    Indicates that the ranking or ordered list begins with a specified entity or value as its first element.
  • B. orderedBy
    Indicates that one entity has placed a request or purchase for another entity, typically specifying who initiated the order.
  • C. orderOf chosen
    Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
  • D. hasRankOrder
    Indicates that one entity is ordered or positioned relative to others according to a specific ranking or sequence.
  • E. rankOverField
    Indicates that one entity’s rank or ordering is determined relative to another entity within a specified field or domain.
  • 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_69f0d62748848190b030d0a703629a7d completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69f7117e55908190a67105e92bc4830f completed May 3, 2026, 9:12 a.m.
PD Predicate disambiguation batch_69f70f380690819090cc34763ba460ed completed May 3, 2026, 9:02 a.m.
Created at: April 28, 2026, 7:30 p.m.