Triple
T13272085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FA Cup 1997–98 with Arsenal F.C. |
E316085
|
entity |
| Predicate | faCupSemiFinalOutcome |
P24543
|
FINISHED |
| Object | Arsenal reached final |
—
|
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 reached final | Statement: [FA Cup 1997–98 with Arsenal F.C., faCupSemiFinalOutcome, Arsenal reached final]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: faCupSemiFinalOutcome Context triple: [FA Cup 1997–98 with Arsenal F.C., faCupSemiFinalOutcome, Arsenal reached final]
-
A.
reachedFA CupSemiFinal
Indicates that an entity (typically a football club) advanced to and participated in the semi-final round of the FA Cup competition.
-
B.
worldCupSemiFinal
Indicates that an event is a semi-final match in the FIFA World Cup tournament, determining which teams advance to the final.
-
C.
semifinalMatchup
Indicates that two competitors or teams are paired to compete against each other in a semifinal round of a tournament or competition.
-
D.
semifinalResult
chosen
Indicates the outcome or score of a semifinal-stage contest or match between competitors.
-
E.
FA CupFinalOpponent
Indicates that one entity was the opposing team faced by the other entity in an FA Cup final match.
- 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_69d806b1d9ac8190852c5571d5bd5f0f |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cfdc9388190af1fdd3cd4717bd8 |
completed | April 11, 2026, 12:59 a.m. |
| PD | Predicate disambiguation | batch_69d98f6535688190a5a4549b7be2d611 |
completed | April 11, 2026, 12:01 a.m. |
Created at: April 9, 2026, 9:26 p.m.