Triple
T35517955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2004–05 Arsenal season |
E1026467
|
entity |
| Predicate | faCupFinalResult |
P131023
|
FINISHED |
| Object | Arsenal win on penalties |
—
|
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: Arsenal win on penalties | Statement: [2004–05 Arsenal season, faCupFinalResult, Arsenal win on penalties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faCupFinalResult Context triple: [2004–05 Arsenal season, faCupFinalResult, Arsenal win on penalties]
-
A.
FA CupFinalScore
Indicates the final match score in an FA Cup competition, specifying how many goals each team scored in the deciding game.
-
B.
FA CupOutcome
chosen
Indicates the result or final status of an entity’s participation in the FA Cup competition.
-
C.
FA CupFinalOpponent
Indicates that one entity was the opposing team faced by the other entity in an FA Cup final match.
-
D.
FA CupWinnerWith
Indicates a relationship where a team is identified as having won the FA Cup together with (i.e., in association with) a particular season, year, or related contextual attribute.
-
E.
reachedFAcupFinal
Indicates that an entity has progressed through the competition to participate in the final match of the FA Cup.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79ec355048190af30123ceb6efa2b |
completed | May 3, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f79e4bdbcc8190be7a0d2cf8a77b64 |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:04 p.m.