Triple
T8484358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago |
E200794
|
entity |
| Predicate | hasNotableTour |
P6082
|
FINISHED |
| Object | co-headlining tours with Earth, Wind & Fire |
—
|
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: co-headlining tours with Earth, Wind & Fire | Statement: [Chicago, hasNotableTour, co-headlining tours with Earth, Wind & Fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableTour Context triple: [Chicago, hasNotableTour, co-headlining tours with Earth, Wind & Fire]
-
A.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
B.
hasNotableExpedition
Indicates that an entity is associated with a significant or noteworthy expedition, journey, or exploratory mission.
-
C.
notableTour
chosen
Indicates that an entity is recognized for having a significant or well-known tour associated with it.
-
D.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
E.
hasDevelopmentTour
Indicates that an entity organizes, participates in, or is associated with a development-focused tour, typically for training, preparation, or early-stage exposure.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe539b70c81909f8f045312f0d5f8 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:12 p.m.