Triple
T4799019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boleyn Ground |
E106786
|
entity |
| Predicate | finalLeagueMatchScore |
P2625
|
FINISHED |
| Object | West Ham United 3–2 Manchester United |
—
|
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: West Ham United 3–2 Manchester United | Statement: [Boleyn Ground, finalLeagueMatchScore, West Ham United 3–2 Manchester United]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalLeagueMatchScore Context triple: [Boleyn Ground, finalLeagueMatchScore, West Ham United 3–2 Manchester United]
-
A.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
finalSecondLegScore
Indicates the score achieved in the second leg of a two-leg competition or matchup once that leg is completed.
-
D.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
-
E.
game6FinalScore
Indicates the final score achieved in the sixth game of a series or sequence of games.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.