Triple
T33550826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sticky & Sweet Tour |
E859326
|
entity |
| Predicate | openedInCountry |
P18098
|
FINISHED |
| Object | Wales |
—
|
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: Wales | Statement: [Sticky & Sweet Tour, openedInCountry, Wales]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedInCountry Context triple: [Sticky & Sweet Tour, openedInCountry, Wales]
-
A.
openingCountry
Indicates the country in which something (such as a business, event, or production) is first opened, launched, or premiered.
-
B.
openedToUnitedStates
Indicates that something (such as a market, service, or access) has been made available or extended to include the United States.
-
C.
openedIn
Indicates that an entity (such as a business, event, or institution) began operating or was inaugurated in a specific time period or location.
-
D.
startsInCountry
Indicates that an entity’s starting point or origin location is situated within a specified country.
-
E.
launchedInCountry
chosen
Indicates that an entity (such as a product, service, or mission) was officially initiated, introduced, or started within a specified country.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd0d0ba5c48190bddb3f0e6637544c |
completed | May 7, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69fd0c4324a8819086c90adf46216e0e |
completed | May 7, 2026, 10:03 p.m. |
Created at: May 1, 2026, 1:39 a.m.