Triple
T14650505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackberrying |
E343968
|
entity |
| Predicate | narrativeSituation |
P115208
|
FINISHED |
| Object | solitary walk |
—
|
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: solitary walk | Statement: [Blackberrying, narrativeSituation, solitary walk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeSituation Context triple: [Blackberrying, narrativeSituation, solitary walk]
-
A.
narrativePremise
Indicates the foundational situation, conflict, or setup that initiates and drives the narrative’s events.
-
B.
narrative
Indicates that one entity tells, presents, or conveys a story or sequence of events about another entity or situation.
-
C.
narrativeDescription
Indicates that one entity provides a textual or spoken account describing the events, context, or details related to another entity.
-
D.
narrativeAction
Indicates an action or event that advances, shapes, or affects the progression of a narrative or story.
-
E.
narrativePassage
Indicates that a segment of text functions as a narrative passage, conveying events, actions, or storytelling rather than exposition, dialogue, or other discourse types.
- 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_69d822e1a2cc81908e5bb93cf61ce3cc |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4ed037c8190a87bf43f839fec05 |
completed | April 14, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69de6576f0208190aa94d995e797ac38 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.