Triple
T31316883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Taylor Swift Touring |
E798620
|
entity |
| Predicate | roleInTours |
P157463
|
FINISHED |
| Object | tour producer |
—
|
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: tour producer | Statement: [Taylor Swift Touring, roleInTours, tour producer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInTours Context triple: [Taylor Swift Touring, roleInTours, tour producer]
-
A.
tourRole
chosen
Indicates the specific function, capacity, or responsibility an entity has within the context of a tour.
-
B.
travelRole
Indicates the specific role or capacity an entity has in relation to a travel activity or journey (e.g., traveler, guide, driver).
-
C.
travelRouteRole
Indicates the specific functional role an entity plays within a travel route, such as origin, destination, or intermediate stop.
-
D.
hasTouringRole
Indicates that an entity holds or performs a specific role or function within a touring context, such as a traveling production, show, or event.
-
E.
roleInAttraction
Indicates the specific function or position an entity holds within the context of a particular attraction or point of interest.
- 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_69f224e1932c81908fef14f7b03a10b7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69ffb1218cb08190a814c7f0833501a7 |
completed | May 9, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69ffb083d6988190b2757e0cfd629b75 |
completed | May 9, 2026, 10:09 p.m. |
Created at: April 29, 2026, 9:15 p.m.