Triple
T33340774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | America Has a Problem |
E853660
|
entity |
| Predicate | tourInclusion |
P127287
|
FINISHED |
| Object | Renaissance World Tour |
—
|
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: Renaissance World Tour | Statement: [America Has a Problem, tourInclusion, Renaissance World Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourInclusion Context triple: [America Has a Problem, tourInclusion, Renaissance World Tour]
-
A.
tourComponentOf
chosen
Indicates that something functions as a constituent part or segment of a larger tour.
-
B.
containsAttraction
Indicates that one entity includes or encompasses an attraction (such as a point of interest, feature, or draw) within its bounds or scope.
-
C.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
D.
tourStaple
Indicates that something is a standard, frequently included element or highlight of a tour.
-
E.
fareIncludes
Indicates that a given fare covers or contains specific components, services, or conditions as part of its overall offering.
- 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_69f3496a1a588190bad9cbe9221144e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:34 a.m.