Triple
T19199133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | …from the Hungry i |
E470055
|
entity |
| Predicate | liveAudiencePresent |
P134836
|
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: […from the Hungry i, liveAudiencePresent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: liveAudiencePresent Context triple: […from the Hungry i, liveAudiencePresent, true]
-
A.
hasLiveAudienceCapability
Indicates that an entity is capable of supporting or engaging with a live, in-person audience.
-
B.
hasAudienceReception
Indicates the relationship between a work or event and how it is received, perceived, or evaluated by its audience.
-
C.
ticketedAudience
Indicates that the audience for an event or activity is required to obtain tickets (i.e., attendance is controlled or limited via ticketing).
-
D.
hasAudienceSize
Indicates the relationship between an entity and the number of people or size of group that receives, views, or engages with it.
-
E.
hasAudienceParticipation
Indicates that an event, performance, or activity involves direct participation or interaction from the audience.
- 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_69d8dd0ad9088190a173b32657ae2e7a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f9967ac081909106aa5ea447e94d |
completed | April 20, 2026, 10:01 a.m. |
| PD | Predicate disambiguation | batch_69e4b9bb158481909478ca2e06f3ba39 |
completed | April 19, 2026, 11:17 a.m. |
| PDg | Predicate description generation | batch_69e4bfe9ef7081908a74a57d1fc731ea |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:07 p.m.