Triple
T32998722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football League Cup 1972–73 |
E844301
|
entity |
| Predicate | includesTwoLeggedTies |
P52770
|
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: [Football League Cup 1972–73, includesTwoLeggedTies, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTwoLeggedTies Context triple: [Football League Cup 1972–73, includesTwoLeggedTies, yes]
-
A.
usesTwoLeggedTies
chosen
Indicates that one entity employs or applies two-legged ties in relation to another entity or context.
-
B.
hasTieDowns
Indicates that an object, structure, or vehicle is equipped with tie-down points or devices for securing loads or attachments.
-
C.
hasTiePossibility
Indicates that a situation, event, or interaction has the potential to end in a tie or draw rather than producing a single winner.
-
D.
typeOfTie
Indicates the specific kind or category of relationship or connection that exists between two entities.
-
E.
tieInWith
Indicates that one thing is connected, coordinated, or made consistent with another, often as part of a combined plan, theme, or schedule.
- 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_69f3494d99988190b502c68926af2c4d |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a0235be932081908857bc3a77c27e7d |
completed | May 11, 2026, 8:02 p.m. |
| PD | Predicate disambiguation | batch_6a022c865dec81909e02b2f330e987e6 |
completed | May 11, 2026, 7:22 p.m. |
Created at: May 1, 2026, 1:22 a.m.