Triple
T28063261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adidas Finale Berlin |
E709172
|
entity |
| Predicate | ballSeries |
P133078
|
FINISHED |
| Object | Adidas Finale series |
—
|
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: Adidas Finale series | Statement: [Adidas Finale Berlin, ballSeries, Adidas Finale series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ballSeries Context triple: [Adidas Finale Berlin, ballSeries, Adidas Finale series]
-
A.
competitionBallFor
Indicates that two or more entities are actively contesting possession or control of the same ball.
-
B.
competitionSeries
Indicates that one entity is a recurring competitive event or series in which the other entity participates or is featured.
-
C.
ballOrStickSport
Indicates that the activity is a sport in which players use a ball, a stick, or a combination of both as primary equipment.
-
D.
coreSeries
chosen
Indicates that one entity is the primary or central series to which another related work or set of works belongs.
-
E.
bowlGame
Indicates that the relationship or event involves a postseason college football bowl game in which a team participates or that is associated with an entity.
- 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_69ef9b6eb6d88190a3fea236eb0f7bed |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f64018804c81909397f6bcf1ab0dea |
completed | May 2, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f637120c008190b2b5adf46f022e48 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 8:41 p.m.