Triple
T3766049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consortium Stade de France |
E82679
|
entity |
| Predicate | operatesVenueFor |
P43750
|
FINISHED |
| Object | sports events |
—
|
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: sports events | Statement: [Consortium Stade de France, operatesVenueFor, sports events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatesVenueFor Context triple: [Consortium Stade de France, operatesVenueFor, sports events]
-
A.
operatesVenue
Indicates that one entity manages and runs the day-to-day operations of a particular venue.
-
B.
venueTypeOperated
chosen
Indicates that an entity operates or manages a venue of a specified type.
-
C.
operatesVenueForLeague
Indicates that an entity manages or runs a venue on behalf of, or for the use of, a particular league.
-
D.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
E.
locatedInOperatedVenue
Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcbfeb52081909c38103beb5dbdcd |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:35 p.m.