Triple
T35711336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lynn Denlon |
E1031866
|
entity |
| Predicate | responsibleForKeepingAlive |
P636
|
FINISHED |
| Object | John Kramer |
—
|
NE NERFINISHED |
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: John Kramer | Statement: [Lynn Denlon, responsibleForKeepingAlive, John Kramer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: responsibleForKeepingAlive Context triple: [Lynn Denlon, responsibleForKeepingAlive, John Kramer]
-
A.
keepsAt
Indicates that an entity stores or maintains another entity at a specific location or position.
-
B.
responsibleFor
chosen
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
C.
requiresStationKeeping
Indicates that maintaining the current position or orbit demands active control or propulsion to counteract external forces.
-
D.
keptOn
Indicates that one entity is stored, placed, or maintained on the surface or location of another entity over a period of time.
-
E.
maintainsThrough
Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
- 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_69f76e0df1d08190965b1c6dff94c391 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.