Triple
T27464648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le MUC |
E693143
|
entity |
| Predicate | previousStadiumNameOfClubReferred |
P901
|
FINISHED |
| Object | Stade Léon-Bollée |
—
|
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: Stade Léon-Bollée | Statement: [Le MUC, previousStadiumNameOfClubReferred, Stade Léon-Bollée]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousStadiumNameOfClubReferred Context triple: [Le MUC, previousStadiumNameOfClubReferred, Stade Léon-Bollée]
-
A.
hostStadiumPreviousName
Indicates that a stadium previously had a different official name before its current one.
-
B.
formerHomeStadium
chosen
Indicates that a venue previously served as the home stadium for a team or organization but no longer holds that status.
-
C.
homeVenueOfPredecessorClubOf
Indicates that a venue served as the home ground for a club that was the predecessor of the referenced club.
-
D.
lastStadium
Indicates that one stadium is the final or most recent stadium associated with a particular entity, such as a team, event, or player.
-
E.
predecessorClubNickname
Indicates that one club’s nickname was previously used by another club that served as its predecessor.
- 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_69ef538105548190a771cc5a0cf8c211 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69fb3425666081908916fcbf3b5dd907 |
completed | May 6, 2026, 12:29 p.m. |
| PD | Predicate disambiguation | batch_69fb2f5f3164819099429c2cc3d24e01 |
completed | May 6, 2026, 12:09 p.m. |
Created at: April 27, 2026, 12:51 p.m.