Triple
T33198852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One More Angel in Heaven |
E849843
|
entity |
| Predicate | hasSettingInStory |
P3538
|
FINISHED |
| Object | Canaan |
—
|
NE NERFINISHED |
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: Canaan | Statement: [One More Angel in Heaven, hasSettingInStory, Canaan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSettingInStory Context triple: [One More Angel in Heaven, hasSettingInStory, Canaan]
-
A.
hasThemeInStory
Indicates that a particular theme is present or plays a significant role within a given story.
-
B.
hasSetting
chosen
Indicates that an entity takes place, occurs, or exists within a particular environment, context, or location.
-
C.
hasManagerInStory
Indicates that one entity serves as the manager of another entity within the context of a specific story or narrative.
-
D.
hasTimeInStory
Indicates that a story element, event, or entity occurs or is present during a specific time or time interval within the narrative.
-
E.
hasStaffTypeInStory
Indicates that a story involves or is associated with a particular type or category of staff.
- 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_69f3495efedc8190843a5728089544b9 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff779e3f0c8190a861f1e4000fd9d9 |
completed | May 9, 2026, 6:06 p.m. |
| PD | Predicate disambiguation | batch_69ff77202638819086e4b9f9c0bc7b31 |
completed | May 9, 2026, 6:04 p.m. |
Created at: May 1, 2026, 1:29 a.m.