Triple
T38106903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jonathan Coulton |
E951538
|
entity |
| Predicate | hasLiveEvent |
P197891
|
FINISHED |
| Object | JoCo Cruise |
—
|
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: JoCo Cruise | Statement: [Jonathan Coulton, hasLiveEvent, JoCo Cruise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveEvent Context triple: [Jonathan Coulton, hasLiveEvent, JoCo Cruise]
-
A.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
B.
hasPublicEventsIn
Indicates that an entity organizes or holds public events within a specified location or context.
-
C.
hasLivePerformanceStatus
Indicates whether an entity’s live performance is occurring, scheduled, completed, or otherwise characterized by a specific performance status.
-
D.
hasLivePerformanceComponent
chosen
Indicates that something includes or involves a live performance as a significant component or feature.
-
E.
hasLivePerformanceSetting
Indicates that an entity is associated with a particular context or environment in which a live performance takes place.
- 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_69f76f065ed08190bdfb1b6d817f5b39 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff234f32888190a1d800a3bda432eb |
completed | May 9, 2026, 12:06 p.m. |
| PD | Predicate disambiguation | batch_69ff228ae9a0819083f4b97c10b923f4 |
completed | May 9, 2026, 12:03 p.m. |
Created at: May 3, 2026, 4:21 p.m.