Triple
T32421203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trainwreck |
E828463
|
entity |
| Predicate | hasTouringHistoryWith |
P110779
|
FINISHED |
| Object | Tenacious D |
—
|
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: Tenacious D | Statement: [Trainwreck, hasTouringHistoryWith, Tenacious D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTouringHistoryWith Context triple: [Trainwreck, hasTouringHistoryWith, Tenacious D]
-
A.
hasTourHistoryWith
chosen
Indicates that two entities have previously participated together in one or more tours or touring events.
-
B.
hasTourHistory
Indicates that an entity has a record of past tours or tour-related activities.
-
C.
hasTour
Indicates that an entity offers, includes, or is associated with a tour experience or guided visit.
-
D.
hasTouringReputation
Indicates that an entity is recognized or reputed for its activities, performance, or presence while traveling or touring.
-
E.
hasTouringRole
Indicates that an entity holds or performs a specific role or function within a touring context, such as a traveling production, show, or event.
- 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_69f3491b28bc8190b75cea7a507f337b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 12:54 a.m.