Triple
T18151434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stade de la Beaujoire |
E434511
|
entity |
| Predicate | notableMatchHosted |
P31101
|
FINISHED |
| Object | 1998 FIFA World Cup group stage matches |
—
|
LITERAL FINISHED |
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: 1998 FIFA World Cup group stage matches | Statement: [Stade de la Beaujoire, notableMatchHosted, 1998 FIFA World Cup group stage matches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMatchHosted Context triple: [Stade de la Beaujoire, notableMatchHosted, 1998 FIFA World Cup group stage matches]
-
A.
notableMatch
Indicates that there exists a particularly significant or noteworthy match or pairing between the related entities.
-
B.
notableMatchVenueFor
chosen
Indicates that a venue is notably associated with hosting a particular match or game.
-
C.
hostCountryOfNotableMatch
Indicates that a country served as the host location for a particular notable match or game.
-
D.
notableTournamentHosted
Indicates that an entity has served as the host or venue for a tournament considered notable or significant.
-
E.
hostedHomeMatchesFor
Indicates that an entity organized and held competitive matches at its own home venue for another entity or group.
- 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_69d8b90aac308190801e2c57d8c5bfe5 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4de38d4e08190bc4d430b70b7e288 |
completed | April 19, 2026, 1:52 p.m. |
| PD | Predicate disambiguation | batch_69e43317d11c81908d1dc14921566b47 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:29 a.m.