Triple
T3989078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurt Caldwell |
E86942
|
entity |
| Predicate | modusOperandi |
P5072
|
FINISHED |
| Object | lures vulnerable young women |
—
|
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: lures vulnerable young women | Statement: [Kurt Caldwell, modusOperandi, lures vulnerable young women]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modusOperandi Context triple: [Kurt Caldwell, modusOperandi, lures vulnerable young women]
-
A.
modalityOf
Indicates that one element specifies the manner, mood, or mode in which the action, event, or state expressed by another element is realized or presented.
-
B.
mode
chosen
Indicates the manner, method, or way in which an action, process, or interaction is carried out or occurs.
-
C.
modulates
Indicates that one entity adjusts, regulates, or alters the intensity, frequency, or effect of another entity or process.
-
D.
modeType
Indicates the specific manner, method, or operational mode in which an action, process, or system is carried out or functions.
-
E.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
- 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_69aed93fd9d4819085d3b2137d2346cb |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefb81040481909b22e4c445ecae0f |
completed | March 9, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_69aef8f692008190bf4d637ffc3d3eaa |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:33 p.m.