Triple
T29664709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Show Me the Way |
E750496
|
entity |
| Predicate | hasNotableLiveAudienceResponse |
P201238
|
FINISHED |
| Object | sing-along chorus |
—
|
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: sing-along chorus | Statement: [Show Me the Way, hasNotableLiveAudienceResponse, sing-along chorus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableLiveAudienceResponse Context triple: [Show Me the Way, hasNotableLiveAudienceResponse, sing-along chorus]
-
A.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
B.
liveAudiencePresent
Indicates that a live, physically present audience is attending the event or performance.
-
C.
hasAudience
Indicates that an entity is intended to be received, viewed, or engaged with by a particular group of people.
-
D.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
E.
hasSpectators
Indicates that an event, activity, or occurrence is being watched or attended by one or more spectators.
- 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_69f0d62418a08190a401b127adf9f8a6 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ffe01c9d3c819084c256bb3c81c0dc |
completed | May 10, 2026, 1:32 a.m. |
| PD | Predicate disambiguation | batch_69ffdfcc78b08190aa4493f13d62a531 |
completed | May 10, 2026, 1:30 a.m. |
| PDg | Predicate description generation | batch_69ffe01be6e88190ac0742a5f74e769e |
completed | May 10, 2026, 1:32 a.m. |
Created at: April 28, 2026, 7 p.m.