Triple
T30042473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aylesbury United F.C. |
E763350
|
entity |
| Predicate | bestFACupRun |
P134512
|
FINISHED |
| Object | reached second round proper |
—
|
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: reached second round proper | Statement: [Aylesbury United F.C., bestFACupRun, reached second round proper]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bestFACupRun Context triple: [Aylesbury United F.C., bestFACupRun, reached second round proper]
-
A.
bestF1Result
Indicates that one result in a set has the highest F1 score (harmonic mean of precision and recall) compared to all other results.
-
B.
FACupTitles
Indicates the number of FA Cup titles that an entity (typically a football club) has won.
-
C.
seasonBestFAcupRound
chosen
Indicates the furthest round of the FA Cup that an entity (such as a team or player) reached in a given season.
-
D.
seriesWinningRunScoredBy
Indicates that a particular run, scored by a specific player, was the decisive run that clinched a series victory for that player’s team.
-
E.
bestUEFACupPerformance
Indicates the highest level or furthest stage an entity has ever reached in UEFA Cup competition.
- 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_69f22470a89c8190be7273297c0e0d19 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f679d92a288190bf4731c3c73a3d57 |
completed | May 2, 2026, 10:25 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:53 p.m.