Triple
T29092961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alicia Keys concert tours chronology |
E734908
|
entity |
| Predicate | includesTour |
P7952
|
FINISHED |
| Object | Songs in A Minor 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: Songs in A Minor Tour | Statement: [Alicia Keys concert tours chronology, includesTour, Songs in A Minor Tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesTour Context triple: [Alicia Keys concert tours chronology, includesTour, Songs in A Minor Tour]
-
A.
hasTour
chosen
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
isPartOfTourDocument
Indicates that a given document belongs to, or is included within, a specific tour-related collection or itinerary.
-
C.
tourWith
Indicates that one entity accompanies another on a tour, sharing the same itinerary or guided experience.
-
D.
hasTourElement
Indicates that something includes or is associated with a specific element or component of a tour.
-
E.
tourOf
Indicates that one entity serves as a guided or organized visit through another entity, typically for exploration, education, or sightseeing.
- 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_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: April 28, 2026, 11:06 a.m.