Triple
T24430044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blaine |
E615973
|
entity |
| Predicate | settingChange |
P156088
|
FINISHED |
| Object | move from California to Cincinnati |
—
|
LITERAL 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: move from California to Cincinnati | Statement: [Blaine, settingChange, move from California to Cincinnati]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingChange Context triple: [Blaine, settingChange, move from California to Cincinnati]
-
A.
setting
Indicates the place, time, or context in which an event, action, or interaction occurs.
-
B.
settingAfter
Indicates that one setting or configuration occurs or is applied after another in a sequence or order.
-
C.
settingControlled
Indicates that one entity regulates, adjusts, or determines the configuration or parameters of another entity.
-
D.
stateSetting
Indicates that one entity establishes, configures, or assigns the state or condition of another entity.
-
E.
featureChange
Indicates a modification in the properties, characteristics, or attributes of an entity between two states or points in time.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296aab8948190b9cb869bab71fb4c |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:15 a.m.