Triple
T36252803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unanswered Prayers |
E891844
|
entity |
| Predicate | hasLiveAudienceSingAlongTradition |
P45833
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Unanswered Prayers, hasLiveAudienceSingAlongTradition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveAudienceSingAlongTradition Context triple: [Unanswered Prayers, hasLiveAudienceSingAlongTradition, yes]
-
A.
hasLivePerformanceTradition
Indicates that there exists an established custom or practice of performing the subject live, typically before an audience.
-
B.
hasAudienceParticipation
chosen
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
-
C.
liveAudiencePresent
Indicates that a live, physically present audience is attending the event or performance.
-
D.
sungToAudience
Indicates that a performance or song was vocally delivered in front of and directed toward an audience.
-
E.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
- 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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fed83b1d188190a318b0ad3003200a |
completed | May 9, 2026, 6:46 a.m. |
| PD | Predicate disambiguation | batch_69fed78e03548190b6e6ad93ae8d131d |
completed | May 9, 2026, 6:43 a.m. |
Created at: May 3, 2026, 4:09 p.m.