Triple
T29808996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Live Earth |
E756907
|
entity |
| Predicate | hadMainVenue |
P50694
|
FINISHED |
| Object | Wembley 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: Wembley Stadium | Statement: [Live Earth, hadMainVenue, Wembley Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadMainVenue Context triple: [Live Earth, hadMainVenue, Wembley Stadium]
-
A.
hasVenueIn
Indicates that an event, activity, or occurrence takes place at a specific venue located within a particular geographic area or location.
-
B.
hasHostedVenue
chosen
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
C.
hasVenueFor
Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
-
D.
hadNoVenue
Indicates that an event, activity, or proceeding took place without any designated or available venue.
-
E.
hasPrincipalVenue
Indicates that an entity has a primary or main venue where its activities, events, or operations predominantly take place.
- 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_69f2245584848190ad4cab1f07752ccb |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6752cfa9481909ae0dbd7fbf8e3eb |
completed | May 2, 2026, 10:05 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:22 p.m.