Triple
T17099264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UEFA Cup 1980–81 |
E414935
|
entity |
| Predicate | decidingFactor |
P23142
|
FINISHED |
| Object | aggregate score over two legs in each round |
—
|
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: aggregate score over two legs in each round | Statement: [UEFA Cup 1980–81, decidingFactor, aggregate score over two legs in each round]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingFactor Context triple: [UEFA Cup 1980–81, decidingFactor, aggregate score over two legs in each round]
-
A.
decisiveFeature
Indicates that one feature or characteristic plays a determining role in deciding an outcome or distinguishing between alternatives.
-
B.
decisiveFor
Indicates that one entity plays a determining or conclusive role in bringing about a particular outcome, decision, or state of another entity.
-
C.
deciderOf
Indicates that one entity is the one who makes decisions or choices regarding another entity or situation.
-
D.
decider
Indicates that an entity is the one who makes a choice or decision in a given situation or process.
-
E.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc00880481909cc0dbc169663a41 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.