Triple
T25274071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National First Division |
E633646
|
entity |
| Predicate | matchOutcomeTiebreakers |
P141055
|
FINISHED |
| Object | goal difference |
—
|
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: goal difference | Statement: [National First Division, matchOutcomeTiebreakers, goal difference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: matchOutcomeTiebreakers Context triple: [National First Division, matchOutcomeTiebreakers, goal difference]
-
A.
useTiebreakers
chosen
Indicates that when primary criteria result in a tie, additional predefined rules or factors are applied to determine a winner or ordering.
-
B.
fairPlayTiebreakerAffectedTeams
Indicates that the teams involved were impacted by a tiebreaker decision based on fair play criteria (such as disciplinary records).
-
C.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
-
D.
usesHeadToHeadAsTiebreaker
Indicates that a head-to-head comparison between entities is used to break a tie in their ranking or outcome.
-
E.
tiebreakerGameLoser
Indicates the player or team that lost a specific tiebreaker game used to resolve a tie in a competition or match.
- 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_69e75a92f48881909974ff9c11150a2e |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48ba5024c8190acce739b3b97bdb8 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:17 p.m.