Triple
T18007918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalia |
E430802
|
entity |
| Predicate | parentOfInFramingStory |
P65999
|
FINISHED |
| Object | Genie’s children |
—
|
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: Genie’s children | Statement: [Dalia, parentOfInFramingStory, Genie’s children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parentOfInFramingStory Context triple: [Dalia, parentOfInFramingStory, Genie’s children]
-
A.
narrativeFrame
Indicates the overarching narrative context or perspective within which events, actions, or relationships are presented or interpreted.
-
B.
parentFrom
Indicates that one entity is the parent (biological, adoptive, or legal) of another entity.
-
C.
framedBy
Indicates that one entity serves as a surrounding boundary or enclosing structure that visually or conceptually frames another entity.
-
D.
narrativeFrameWork
Indicates a relationship where one element provides the structural or conceptual framework within which another element’s narrative is organized, interpreted, or presented.
-
E.
motherInStory
chosen
Indicates that one entity is the mother of another entity within the context of a particular story or narrative.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b51d44088190bfcd35e532a4c02a |
completed | April 19, 2026, 10:57 a.m. |
| PD | Predicate disambiguation | batch_69e3f90039e4819080527f860dca042e |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:24 a.m.