Triple
T33701602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garry Essendine |
E863467
|
entity |
| Predicate | isFrequentlyOnTour |
P177214
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Garry Essendine, isFrequentlyOnTour, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFrequentlyOnTour Context triple: [Garry Essendine, isFrequentlyOnTour, true]
-
A.
isFrequentlyPerformedOnTourBy
Indicates that an action or piece (such as a song, routine, or performance) is regularly and commonly carried out by an entity while they are on tour.
-
B.
isMajorOnTour
Indicates that an entity is a primary or headlining participant in a tour or touring event.
-
C.
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.
-
D.
hasTouringAct
Indicates that an entity (such as a venue, festival, or organization) features, hosts, or is associated with a touring performance act.
-
E.
workedOnTour
Indicates that an entity participated in or contributed work to a particular tour.
- F. None of above. chosen
Provenance (4 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:43 a.m.