Triple
T14121494
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Experiment 626 |
E339914
|
entity |
| Predicate | laterPurposeInFiction |
P80898
|
FINISHED |
| Object | protecting his family |
—
|
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: protecting his family | Statement: [Experiment 626, laterPurposeInFiction, protecting his family]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterPurposeInFiction Context triple: [Experiment 626, laterPurposeInFiction, protecting his family]
-
A.
laterSettingOfFiction
Indicates that one fictional work is set chronologically later than another within a shared narrative or story world.
-
B.
fictionalUse
Indicates that one entity makes use of another within a fictional or imaginary context, rather than in real-world usage.
-
C.
literaryPurpose
Indicates the intended function, effect, or communicative goal that a text or passage is meant to achieve within a literary context.
-
D.
narrativePurpose
chosen
Indicates the role or function that something serves within the structure or progression of a narrative.
-
E.
usedInFictionalWork
Indicates that something (such as a concept, object, or character) appears or is employed within a specific fictional work.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de60942a588190beff0058a92f7051 |
completed | April 14, 2026, 3:43 p.m. |
| PD | Predicate disambiguation | batch_69de05b5e7a08190a16be9ad8b92b80c |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.