Triple
T36402893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup with Manchester United 1962–63 |
E896677
|
entity |
| Predicate | opponentClub |
P106971
|
FINISHED |
| Object | Leicester City F.C. |
—
|
NE NERFINISHED |
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: Leicester City F.C. | Statement: [FA Cup with Manchester United 1962–63, opponentClub, Leicester City F.C.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentClub Context triple: [FA Cup with Manchester United 1962–63, opponentClub, Leicester City F.C.]
-
A.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
B.
associatedClub1
Indicates that an entity has a primary or first-listed association with a particular club or organization.
-
C.
teamOpponent
chosen
Indicates that two teams are competing against each other as opponents in a game or match.
-
D.
associatedClub2
Indicates that an entity has a secondary or additional affiliation or membership with a particular club.
-
E.
opponentStarPlayerTeam
Indicates that the referenced team is the one for which the opponent’s star player plays.
- 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_69f76e53b81081908d3b81860593f38a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c475c58c8190a883554231e88c88 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:10 p.m.