Triple
T25819734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hinckley United F.C. |
E650366
|
entity |
| Predicate | playedInCup |
P10753
|
FINISHED |
| Object | FA Cup |
—
|
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: FA Cup | Statement: [Hinckley United F.C., playedInCup, FA Cup]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInCup Context triple: [Hinckley United F.C., playedInCup, FA Cup]
-
A.
involvesCupMatches
Indicates that the relationship or event includes or pertains to matches played within a cup or knockout-style competition.
-
B.
playedInTournament
chosen
Indicates that an entity participated as a competitor or player in a specific tournament.
-
C.
playedFor
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
hasCupTieEntry
Indicates that an entity has an associated entry or participation record in a cup-style competition or knockout tournament.
-
E.
playedInConference
Indicates that an entity (typically a team or player) participated in games within a specific conference during a season or time period.
- 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_69e7ab367fcc8190a5ff1e7f3da046a4 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
Created at: April 22, 2026, 7:28 a.m.