Triple
T33210246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luther Krank |
E850135
|
entity |
| Predicate | initiallyPlansTo |
P67155
|
FINISHED |
| Object | skip Christmas |
—
|
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: skip Christmas | Statement: [Luther Krank, initiallyPlansTo, skip Christmas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initiallyPlansTo Context triple: [Luther Krank, initiallyPlansTo, skip Christmas]
-
A.
planned
Indicates that an entity has intentionally arranged or scheduled another entity or event to occur in the future.
-
B.
intendsTo
Indicates that one entity has the purpose, plan, or desire to perform an action involving another entity or outcome.
-
C.
originallyPlannedFor
chosen
Indicates that something was initially intended, designed, or scheduled to be used for or associated with a particular purpose, event, or entity, regardless of what ultimately occurred.
-
D.
plannedVia
Indicates that something is arranged, organized, or scheduled by means of a particular method, process, or intermediary.
-
E.
plannedIn
Indicates that an event, activity, or process is scheduled or arranged to occur within a specific context, timeframe, or plan.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 1, 2026, 1:30 a.m.