Triple
T8898994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Knebworth |
E211876
|
entity |
| Predicate | concertsHosted |
P50694
|
FINISHED |
| Object | Queen at Knebworth 1986 |
—
|
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: Queen at Knebworth 1986 | Statement: [Knebworth, concertsHosted, Queen at Knebworth 1986]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: concertsHosted Context triple: [Knebworth, concertsHosted, Queen at Knebworth 1986]
-
A.
hasHostedVenue
chosen
Indicates that a particular venue has served as the location for hosting a specific event or activity.
-
B.
hostedDuring
Indicates that one entity hosted, organized, or held another entity (such as an event or activity) within a specified time period.
-
C.
notableConcert
Indicates that a concert event is recognized as particularly significant, memorable, or influential in some notable way.
-
D.
hasLiveMusic
Indicates that a place or event features live musical performances as part of its offerings.
-
E.
hasCulturalEvent
Indicates that a cultural event (such as a festival, performance, or exhibition) takes place in, is associated with, or is hosted by a given 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc642618908190b3df50cbbabff93d |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5c2bfb38819083d5eb1af8ccf4d6 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:54 p.m.