Triple

T15672710
Position Surface form Disambiguated ID Type / Status
Subject Corinthian F.C. E377355 entity
Predicate scoredNotableResult P56419 FINISHED
Object large-margin victories over professional clubs (historically recorded) 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: large-margin victories over professional clubs (historically recorded) | Statement: [Corinthian F.C., scoredNotableResult, large-margin victories over professional clubs (historically recorded)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: scoredNotableResult
Context triple: [Corinthian F.C., scoredNotableResult, large-margin victories over professional clubs (historically recorded)]
  • A. notableWin chosen
    Indicates that one entity achieved a particularly significant or distinguished victory over another or in a specific event.
  • B. notableOutcome
    Indicates that an action, event, or entity leads to or is associated with a significant, noteworthy result or consequence.
  • C. notableWinType
    Indicates that the relationship specifies the particular category or type of a notable victory associated with an entity.
  • D. notablePlay
    Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
  • E. notableMatch
    Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
  • 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_69d85cd2e28481909d4e975bee20872f completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69e04f13b1b08190beabc9f4098aa096 completed April 16, 2026, 2:53 a.m.
PD Predicate disambiguation batch_69deda8b36a4819081cb5708fe77ef51 completed April 15, 2026, 12:23 a.m.
Created at: April 10, 2026, 4:16 a.m.