Triple
T30682342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Srivaddhanaprabha family |
E781086
|
entity |
| Predicate | associatedStadiumNamingRights |
P84804
|
FINISHED |
| Object | King Power Stadium |
E219472
|
NE 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: King Power Stadium | Statement: [Srivaddhanaprabha family, associatedStadiumNamingRights, King Power Stadium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedStadiumNamingRights Context triple: [Srivaddhanaprabha family, associatedStadiumNamingRights, King Power Stadium]
-
A.
namingRightsCity
Indicates that a city holds the naming rights associated with a particular entity, venue, or event.
-
B.
acquiredNamingRightsYear
Indicates the year in which an entity obtained the naming rights to another entity (such as a venue, event, or organization).
-
C.
associatedStadiums
Indicates that there is a relationship linking an entity to one or more stadiums with which it is connected or affiliated.
-
D.
namingRightsLocation
Indicates that an entity holds the naming rights specifically for a given location or venue.
-
E.
sponsorOfStadiumName
chosen
Indicates that an entity serves as the naming-rights sponsor for a particular stadium.
- F. None of above.
Provenance (4 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2b074dfda88190bfc8521eb15f3ef7 |
completed | June 11, 2026, 7:06 p.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:33 p.m.