Triple
T31192549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockshow |
E795220
|
entity |
| Predicate | documentsTour |
P56630
|
FINISHED |
| Object | Wings Over the 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: Wings Over the World tour | Statement: [Rockshow, documentsTour, Wings Over the World tour]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentsTour Context triple: [Rockshow, documentsTour, Wings Over the World tour]
-
A.
tourDocumented
chosen
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
-
B.
documentsJourneyTo
Indicates that one entity records or describes the travel, route, or progression of another entity from one place or state to another.
-
C.
isPartOfTourDocument
Indicates that a given document belongs to, or is included within, a specific tour-related collection or itinerary.
-
D.
documentsJourneyFrom
Indicates that one entity records or describes the progression, experiences, or development originating from another entity.
-
E.
documentsJourneyOf
Indicates that one entity records, narrates, or chronicles the progression, experiences, or development of another entity over time.
- 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_69f224d7a6a481908187c4362a8a525f |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 29, 2026, 9:08 p.m.