Triple
T1348141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt Lewin |
E28817
|
entity |
| Predicate | threeStageModelOfChange |
P9657
|
FINISHED |
| Object | unfreeze-change-refreeze |
—
|
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: unfreeze-change-refreeze | Statement: [Kurt Lewin, threeStageModelOfChange, unfreeze-change-refreeze]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threeStageModelOfChange Context triple: [Kurt Lewin, threeStageModelOfChange, unfreeze-change-refreeze]
-
A.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
-
B.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
C.
thirdStageEngineType
Indicates the specific type or model of engine used in the third stage of a multi-stage launch vehicle or rocket.
-
D.
energyStage
Indicates the specific phase or level within an energy-related process, cycle, or transformation that an entity is currently in.
-
E.
secondStage
Indicates that something functions as the subsequent or follow-up stage in a multi-stage process or sequence.
- 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_69a498571d248190a0ac9eb02d97097f |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c2418e38819094683d6e1efc6e56 |
completed | March 1, 2026, 10:48 p.m. |
| PD | Predicate disambiguation | batch_69a4bef5857c81909ae984feb85a26ca |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.