Triple
T26319300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Psalms Jackson |
E662059
|
entity |
| Predicate | settingFictional |
P67881
|
FINISHED |
| Object | American West |
—
|
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: American West | Statement: [Psalms Jackson, settingFictional, American West]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingFictional Context triple: [Psalms Jackson, settingFictional, American West]
-
A.
settingOfFictionalLife
chosen
Indicates that a particular place or environment serves as the primary backdrop or context in which a fictional character’s life and experiences occur.
-
B.
laterSettingOfFiction
Indicates that one fictional work is set chronologically later than another within a shared narrative or story world.
-
C.
fictionalSon
Indicates that one entity is portrayed as the son of another entity within a fictional or narrative context.
-
D.
fictionalContent
Indicates that one entity is content whose subject matter, events, or characters are imaginary or invented rather than factual.
-
E.
fictionalField
Indicates that the subject is associated with a fictional or imaginary field, domain, or area rather than a real-world one.
- 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_69ee812e73048190aae587f1d51e5a06 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:27 p.m.