Triple
T36103582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade du Ray |
E1044288
|
entity |
| Predicate | replacedByStadiumForClub |
P61007
|
FINISHED |
| Object | Allianz Riviera |
—
|
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: Allianz Riviera | Statement: [Stade du Ray, replacedByStadiumForClub, Allianz Riviera]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedByStadiumForClub Context triple: [Stade du Ray, replacedByStadiumForClub, Allianz Riviera]
-
A.
replacedStadiumForTeam
chosen
Indicates that one stadium succeeded and took over the role of another as the home venue for a particular team.
-
B.
replacedByAsMainFootballVenue
Indicates that one football venue has been superseded by another as the primary location for hosting football events.
-
C.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
D.
previousNameOfStadiumOfClub
Indicates that one entity is a former name previously used for the stadium belonging to a particular sports club.
-
E.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fe21b0cba48190b56c39e9f1c0eafa |
completed | May 8, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69fe204576848190aecf204e2adba5dc |
completed | May 8, 2026, 5:41 p.m. |
Created at: May 3, 2026, 4:08 p.m.