Triple
T35301096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magic Weekend |
E1019505
|
entity |
| Predicate | hasBeenHostedAt |
P104984
|
FINISHED |
| Object | Millennium Stadium |
—
|
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: Millennium Stadium | Statement: [Magic Weekend, hasBeenHostedAt, Millennium Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBeenHostedAt Context triple: [Magic Weekend, hasBeenHostedAt, Millennium Stadium]
-
A.
hasBeenHostedIn
chosen
Indicates that an event, show, or activity took place or was conducted at a particular location or venue in the past.
-
B.
hasHostedVenue
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
C.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
D.
hostedOn
Indicates that one entity operates, resides, or is made available on another entity that provides the underlying platform or infrastructure.
-
E.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:03 p.m.