Triple
T32776395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Claire Keesey |
E838218
|
entity |
| Predicate | unknowinglyDates |
P175107
|
FINISHED |
| Object | bank robber |
—
|
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: bank robber | Statement: [Claire Keesey, unknowinglyDates, bank robber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: unknowinglyDates Context triple: [Claire Keesey, unknowinglyDates, bank robber]
-
A.
dateOf
Indicates that one entity specifies the calendar date associated with another entity, such as when it occurred, was created, or is scheduled.
-
B.
uncertainBirthDate
Indicates that the exact birth date of an entity is not known or is only approximately specified.
-
C.
hasUnknownDeathDate
Indicates that the entity’s date of death is not known or not specified.
-
D.
dateHidden
Indicates that the date associated with an item, event, or record is intentionally concealed or not displayed.
-
E.
unRecognitionDate
Indicates the date on which a previously recognized status, entity, or relationship is officially withdrawn or no longer acknowledged.
- F. None of above. chosen
Provenance (4 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_69f3493a824c8190938489ba69041d08 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6ce6c76bc8190b865343d3f5810c9 |
completed | May 3, 2026, 4:26 a.m. |
Created at: May 1, 2026, 1:13 a.m.