Triple
T27776875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Circus Live |
E699215
|
entity |
| Predicate | featuresTourLocation |
P7690
|
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: [The Circus Live, featuresTourLocation, Wembley Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresTourLocation Context triple: [The Circus Live, featuresTourLocation, Wembley Stadium]
-
A.
tourismFeature
Indicates that something serves as an attraction, amenity, or point of interest relevant to tourism or visitors.
-
B.
featuresLocation
chosen
Indicates that something is characterized by or includes a specific location as one of its notable attributes.
-
C.
tourInformation
Indicates that an entity provides details or data about a tour, such as schedule, itinerary, or features.
-
D.
tourStaple
Indicates that something is a standard, frequently included element or highlight of a tour.
-
E.
tourismCharacteristic
Indicates that something has a specific feature, quality, or attribute relevant to tourism, such as what makes a place, service, or activity notable or suitable for tourists.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
Created at: April 27, 2026, 5:06 p.m.