Triple
T29092969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicia Keys concert tours chronology |
E734908
|
entity |
| Predicate | includesTourType |
P1769
|
FINISHED |
| Object | headlining concert tours |
—
|
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: headlining concert tours | Statement: [Alicia Keys concert tours chronology, includesTourType, headlining concert tours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTourType Context triple: [Alicia Keys concert tours chronology, includesTourType, headlining concert tours]
-
A.
includesResortType
Indicates that one entity contains or offers a specific type or category of resort as part of its overall composition or services.
-
B.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
C.
containsRideType
Indicates that one entity includes or offers a specific type or category of ride as part of its available options.
-
D.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
E.
tourismType
chosen
Indicates the specific category or kind of tourism activity or experience associated with an 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: April 28, 2026, 11:06 a.m.