Triple
T32323253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Case of Conscience |
E825832
|
entity |
| Predicate | partOneSetting |
P200608
|
FINISHED |
| Object | Lithia |
—
|
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: Lithia | Statement: [A Case of Conscience, partOneSetting, Lithia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOneSetting Context triple: [A Case of Conscience, partOneSetting, Lithia]
-
A.
partialSettingOf
Indicates that one entity establishes or configures only some aspects or components of another entity, rather than defining it completely.
-
B.
primarySetting
Indicates that one entity serves as the main or central location, context, or environment in which the other entity’s events or activities primarily take place.
-
C.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
D.
coversSetting
Indicates that one entity includes or addresses a particular setting or context within its scope.
-
E.
primarySettingOf
Indicates that a location or context serves as the main or principal setting in which an entity (such as a story, event, or activity) takes place.
- F. None of above. chosen
Provenance (4 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_69f34912d0c48190bba75770660320e9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
| PDg | Predicate description generation | batch_69ff9b19f254819099bb9c034d2b399b |
completed | May 9, 2026, 8:37 p.m. |
Created at: May 1, 2026, 12:47 a.m.