Triple
T27925618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Finale Paris |
E707823
|
entity |
| Predicate | finalScoreMatch |
P2625
|
FINISHED |
| Object | FC Barcelona 2–1 Arsenal FC |
—
|
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: FC Barcelona 2–1 Arsenal FC | Statement: [Adidas Finale Paris, finalScoreMatch, FC Barcelona 2–1 Arsenal FC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalScoreMatch Context triple: [Adidas Finale Paris, finalScoreMatch, FC Barcelona 2–1 Arsenal FC]
-
A.
finalOfficialMatchScore
Indicates the conclusive, authoritative score assigned to a match after all reviews, adjustments, or validations are completed.
-
B.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
C.
resultOfMatch
Indicates that one entity is the outcome or product produced by a particular match or matching event involving another entity.
-
D.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
E.
finalOfficialMatch
Indicates that a given match is the last officially recognized contest or game in a defined series, season, tournament, or career.
- 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_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 27, 2026, 6:59 p.m.