Triple
T27464647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le MUC |
E693143
|
entity |
| Predicate | associatedStadiumOfClubReferred |
P80805
|
FINISHED |
| Object | Stade Marie-Marvingt |
—
|
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 Marie-Marvingt | Statement: [Le MUC, associatedStadiumOfClubReferred, Stade Marie-Marvingt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStadiumOfClubReferred Context triple: [Le MUC, associatedStadiumOfClubReferred, Stade Marie-Marvingt]
-
A.
associatedStadiums
chosen
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
B.
locatedAtStadiumOfClub
Indicates that something is situated in the stadium that belongs to or is used by a particular sports club.
-
C.
parentClubStadium
Indicates that a stadium serves as the home venue associated with a particular parent club.
-
D.
leagueVenue
Indicates that a particular venue is used as the location where a league holds its games or events.
-
E.
associatedWithStadiumLocation
Indicates a relationship where an entity is connected or linked to the location of a specific stadium.
- 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_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 27, 2026, 12:51 p.m.