Triple
T12805514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TFF First League |
E306133
|
entity |
| Predicate | usesGoalDifferenceTiebreak |
P91093
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [TFF First League, usesGoalDifferenceTiebreak, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesGoalDifferenceTiebreak Context triple: [TFF First League, usesGoalDifferenceTiebreak, yes]
-
A.
usesGoalDifferenceTiebreaker
chosen
Indicates that when entities are tied, their ranking or outcome is decided based on the difference between goals scored and goals conceded.
-
B.
leagueGoalDifference
Indicates the numerical difference between goals scored and goals conceded by an entity within a league competition.
-
C.
usesAwayGoalsRule
Indicates that a competition or match outcome is decided using the away goals rule, where goals scored by a team in away games serve as a tiebreaker.
-
D.
penaltyGoalPoints
Indicates that points are awarded for a goal scored from a penalty situation.
-
E.
equalisingGoalTeam
Indicates that a team scores a goal which brings the score level with the opposing team.
- 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_69d7bdf366888190a8cccb982606889c |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e7f370c8190b3fc39c1b63394c6 |
completed | April 10, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69d9640ed7448190b276e7fab649f7d2 |
completed | April 10, 2026, 8:56 p.m. |
Created at: April 9, 2026, 5:31 p.m.