Triple
T34781103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Snake (poem) |
E1002662
|
entity |
| Predicate | hasNarratorAction |
P110520
|
FINISHED |
| Object | throws a log at the snake |
—
|
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: throws a log at the snake | Statement: [Snake (poem), hasNarratorAction, throws a log at the snake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNarratorAction Context triple: [Snake (poem), hasNarratorAction, throws a log at the snake]
-
A.
hasNarration
Indicates that an entity provides spoken or written commentary or storytelling for another entity, such as a work, event, or scene.
-
B.
hasNarrativeRole
Indicates that an entity participates in a narrative with a specific functional role (e.g., protagonist, antagonist, narrator) relative to the story.
-
C.
hasNarratorEmotion
Indicates that a narrator expresses or experiences a particular emotion in relation to a described event, situation, or narrative segment.
-
D.
hasCoNarrator
Indicates that two or more entities share the role of narrating the same work, event, or story together.
-
E.
hasNarrativeEvent
chosen
Indicates that one entity includes, contains, or is associated with a specific narrative event within a story or sequence of events.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 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, 3:59 p.m.