Triple
T6867878
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mary Kane |
E158457
|
entity |
| Predicate | decisionMotivation |
P23142
|
FINISHED |
| Object | desire to secure Charles Foster Kane’s financial future |
—
|
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: desire to secure Charles Foster Kane’s financial future | Statement: [Mary Kane, decisionMotivation, desire to secure Charles Foster Kane’s financial future]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisionMotivation Context triple: [Mary Kane, decisionMotivation, desire to secure Charles Foster Kane’s financial future]
-
A.
decisionMaking
Indicates the process by which an entity evaluates options and selects a course of action among alternatives.
-
B.
decisionBasis
chosen
Indicates the underlying reason, criterion, or rationale on which a decision is made.
-
C.
decisionEffect
Indicates that one decision leads to, influences, or determines a particular outcome or consequence.
-
D.
decisionType
Indicates the specific category or nature of a decision associated with an entity or event.
-
E.
decisionOutput
Indicates that a decision-making process produces or yields a particular outcome or result.
- 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_69c68831e3648190a643c328122e4d43 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6da3ce95081909a424ac04bc7fa07 |
completed | March 27, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b168908190b2f7c724b1bc7fc9 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:21 p.m.