Triple
T37360735
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 1991–92 |
E927568
|
entity |
| Predicate | winnerBy |
P20470
|
FINISHED |
| Object | away goals rule |
—
|
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: away goals rule | Statement: [UEFA Cup 1991–92, winnerBy, away goals rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winnerBy Context triple: [UEFA Cup 1991–92, winnerBy, away goals rule]
-
A.
winnerWith
Indicates that one entity is the winner in a context or event specifically in association or combination with another entity.
-
B.
wonBy
chosen
Indicates that a contest, game, or competition is decided in favor of a particular participant or side.
-
C.
winnerDeterminedAs
Indicates that a specific entity has been officially recognized or decided as the winner in a given context or competition.
-
D.
winnerWins
Indicates that the entity identified as the winner achieves victory over another entity or in a specified competition or event.
-
E.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
- 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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: May 3, 2026, 4:16 p.m.