Triple
T4351954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AFC Champions League |
E98045
|
entity |
| Predicate | usesAwayGoalsRuleHistorically |
P52769
|
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: [AFC Champions League, usesAwayGoalsRuleHistorically, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAwayGoalsRuleHistorically Context triple: [AFC Champions League, usesAwayGoalsRuleHistorically, yes]
-
A.
usesAwayGoalsRule
chosen
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.
-
B.
seasonRecordContextAway
Indicates the performance or statistical record of an entity specifically in away games over the course of a season.
-
C.
numberOfGoals
Indicates the total count of goals scored or achieved by an entity in a given context.
-
D.
leagueGoalsAgainst
Indicates the number of goals a team has conceded in league competition against its opponents.
-
E.
leagueGoalDifference
Indicates the numerical difference between goals scored and goals conceded by an entity within a league competition.
- 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_69b3454965f881908c41190bb22f0e4b |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351ab03488190a8900de98fb4a00e |
completed | March 12, 2026, 11:52 p.m. |
| PD | Predicate disambiguation | batch_69b34f51ed7c8190b7bf5f44b56b730d |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:15 p.m.