Triple
T32589708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Nonesuch |
E833030
|
entity |
| Predicate | audienceReactionInStory |
P150774
|
FINISHED |
| Object | initial curiosity |
—
|
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: initial curiosity | Statement: [The Royal Nonesuch, audienceReactionInStory, initial curiosity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audienceReactionInStory Context triple: [The Royal Nonesuch, audienceReactionInStory, initial curiosity]
-
A.
hasAudienceReactionType
chosen
Indicates the specific type or category of reaction an audience has in response to something (e.g., content, an event, or a performance).
-
B.
causedReaction
Indicates that one entity’s action or state brought about a specific reaction or response in another entity.
-
C.
audienceWithinStory
Indicates that an audience exists as an internal, in-story observer or listener within the narrative itself, rather than outside it.
-
D.
featuresReaction
Indicates that one entity exhibits, displays, or includes a particular reaction associated with another entity or context.
-
E.
isAReactionTo
Indicates that one event, action, or state occurs as a direct response or consequence of another.
- 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_69f34929ff648190aded9424aa7564ae |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 1:04 a.m.