Triple
T32006629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heysel metro station |
E817285
|
entity |
| Predicate | servesVenueType |
P10640
|
FINISHED |
| Object | sports stadium |
—
|
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 stadium | Statement: [Heysel metro station, servesVenueType, sports stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servesVenueType Context triple: [Heysel metro station, servesVenueType, sports stadium]
-
A.
servesVenue
Indicates that an entity provides services or functions in support of a particular venue.
-
B.
servesType
Indicates that one entity provides, offers, or is used to deliver a particular type, category, or kind of thing or service.
-
C.
refersToVenueType
chosen
Indicates that one entity specifies or identifies the type or category of venue associated with another entity.
-
D.
servesEventType
Indicates that an entity provides or supports a particular type or category of event.
-
E.
isRegularVenueFor
Indicates that a location is commonly or routinely used as the venue for a particular event, activity, or entity’s gatherings.
- 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_69f348f8ce388190ae84376b1f348f12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff0e9c75208190a4423261f00b79b3 |
completed | May 9, 2026, 10:38 a.m. |
| PD | Predicate disambiguation | batch_69ff0e07f08481909c4ae322632a6bf0 |
completed | May 9, 2026, 10:35 a.m. |
Created at: May 1, 2026, 12:15 a.m.