Triple
T27972674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosario derby |
E706404
|
entity |
| Predicate | homeTeamAtEstadioGiganteDeArroyito |
P47009
|
FINISHED |
| Object | Rosario Central |
—
|
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: Rosario Central | Statement: [Rosario derby, homeTeamAtEstadioGiganteDeArroyito, Rosario Central]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeTeamAtEstadioGiganteDeArroyito Context triple: [Rosario derby, homeTeamAtEstadioGiganteDeArroyito, Rosario Central]
-
A.
opponentsAtRiverPlate
Indicates that two entities are opposing teams or competitors in a match or event taking place at River Plate’s venue.
-
B.
hostTeamStadium
chosen
Indicates that a particular team plays its home games at a specified stadium.
-
C.
finalHostTeam
Indicates that a team is designated as the host team for the final match or final stage of a competition.
-
D.
homeTeamFIFAcode
Indicates the FIFA country code assigned to the team designated as the home team in a match.
-
E.
homeTeam
Indicates that one entity is designated as the home team in a game, match, or sporting event involving another 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_69ef96b7f330819090f315318ba6977e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 7:39 p.m.