Triple
T30893298
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Katharine Gun |
E786957
|
entity |
| Predicate | chargeOutcomeDate |
P170276
|
FINISHED |
| Object | 2004-02-25 |
—
|
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: 2004-02-25 | Statement: [Katharine Gun, chargeOutcomeDate, 2004-02-25]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargeOutcomeDate Context triple: [Katharine Gun, chargeOutcomeDate, 2004-02-25]
-
A.
chargeDate
Indicates the date on which a financial charge or billing action is applied or recorded.
-
B.
chargesOutcome
Indicates the result or disposition of formal charges brought in a legal or disciplinary context (e.g., convicted, dismissed, reduced, or acquitted).
-
C.
dateFinalized
Indicates that a specific date has been set as the official or final completion/confirmation time for an associated event, decision, or record.
-
D.
settledDate
Indicates the date on which a transaction, obligation, or agreement is fully completed and finalized.
-
E.
acknowledgmentDate
Indicates the date on which an acknowledgment of something (such as receipt, notice, or information) is formally recorded or recognized.
- 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_69f224bbfa7c81908448e0c261c523e3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f692391694819096143e91732b126b |
completed | May 3, 2026, 12:09 a.m. |
| PD | Predicate disambiguation | batch_69f68b7ec098819080480998038de940 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68c517f308190873c1c7e05a0c6d0 |
completed | May 2, 2026, 11:44 p.m. |
Created at: April 29, 2026, 8:49 p.m.