Triple
T32323456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A Case of Conscience |
E825837
|
entity |
| Predicate | firstPartSetting |
P200608
|
FINISHED |
| Object | Lithia |
E2002406
|
NE 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: Lithia | Statement: [A Case of Conscience, firstPartSetting, Lithia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPartSetting Context triple: [A Case of Conscience, firstPartSetting, Lithia]
-
A.
partOneSetting
chosen
Indicates that one entity specifies or defines the setting or context for the first part of another entity (such as a work, event, or process).
-
B.
firstPartValue
Indicates that the subject entity represents the initial or leading portion of a larger value, sequence, or composite data item.
-
C.
firstPartType
Indicates that one entity is the initial segment or component type within a larger composite or sequence of parts.
-
D.
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.
-
E.
firstPartFormat
Indicates that the subject entity is the initial segment or portion in the overall format or structured sequence of something.
- F. None of above.
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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a33e899cfa481909aade8dd99bc484a |
completed | June 18, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:47 a.m.