Triple
T4068578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centennial Olympic Park bombing |
E86587
|
entity |
| Predicate | perpetratorArrestDate |
P3170
|
FINISHED |
| Object | 2003-05-31 |
—
|
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: 2003-05-31 | Statement: [Centennial Olympic Park bombing, perpetratorArrestDate, 2003-05-31]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: perpetratorArrestDate Context triple: [Centennial Olympic Park bombing, perpetratorArrestDate, 2003-05-31]
-
A.
dateOfArrest
chosen
Indicates the specific date on which an entity was formally arrested by an authority.
-
B.
arrestedAt
Indicates that an entity was apprehended or taken into custody at a specific location or during a specific event or time.
-
C.
arrestedFor
Indicates that an authority has taken someone into custody because they are suspected or accused of committing a specified offense or wrongdoing.
-
D.
dateOfConviction
Indicates the specific calendar date on which a person or entity was formally found guilty of an offense.
-
E.
attemptedArrestBy
Indicates that one entity tried, but may not have succeeded, to place another entity under arrest.
- 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_69aed93ebe448190a1f1686e28740ac9 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefbf8f33c8190a6afca1830f35485 |
completed | March 9, 2026, 4:57 p.m. |
| PD | Predicate disambiguation | batch_69aef9061d2481908307cafc9e9b32c0 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.