Triple
T36122101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henrickson family compound |
E1044771
|
entity |
| Predicate | hasPlotEvents |
P110520
|
FINISHED |
| Object | family dinners |
—
|
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: family dinners | Statement: [Henrickson family compound, hasPlotEvents, family dinners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlotEvents Context triple: [Henrickson family compound, hasPlotEvents, family dinners]
-
A.
hasPlot
Indicates that an entity (such as a narrative work) possesses or is associated with a specific storyline or sequence of events.
-
B.
hasNarrativeEvent
chosen
Indicates that one entity includes, contains, or is associated with a specific narrative event within a story or sequence of events.
-
C.
hasAdventurePlot
Indicates that a work’s storyline centers on an adventure, typically involving exciting, risky, or exploratory events and journeys.
-
D.
hasMainPlotElement
Indicates that one entity serves as a central or primary plot element within the narrative of another entity.
-
E.
hasFictionalEventType
Indicates that something is associated with, characterized by, or classified under a particular type or category of fictional event.
- 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_69f76e356c908190abc6ca1e6a05b011 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: May 3, 2026, 4:08 p.m.