Triple
T38443025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sweet Chariot |
E906552
|
entity |
| Predicate | narrativeWorkOn |
P108972
|
FINISHED |
| Object | Sally Rose |
—
|
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: Sally Rose | Statement: [Sweet Chariot, narrativeWorkOn, Sally Rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeWorkOn Context triple: [Sweet Chariot, narrativeWorkOn, Sally Rose]
-
A.
narrativeModeInWork
Indicates the narrative mode or point of view used within a specific literary or artistic work.
-
B.
narrativeSettingOfWork
Indicates that a particular place, time, or context serves as the narrative setting in which a work’s story or events occur.
-
C.
narrativeFocusOfWork
Indicates that a particular element (such as a character, event, or theme) is the primary narrative focus or central subject of a given work.
-
D.
worksOnStoryAbout
Indicates that one entity is actively engaged in creating, developing, or contributing to a story whose subject or focus is another entity.
-
E.
creativeWorkOn
chosen
Indicates a relationship where an entity has created, contributed to, or worked on a particular creative work (such as a book, artwork, film, or other intellectual product).
- 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_69f76e72878c8190a692836c8b01b58b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd6dbd1b648190b1a0b391c03aebc5 |
completed | May 8, 2026, 4:59 a.m. |
| PD | Predicate disambiguation | batch_69fd6a9020548190bbfa845360ac85fb |
completed | May 8, 2026, 4:46 a.m. |
Created at: May 3, 2026, 4:31 p.m.