Triple
T1130784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | How to Dismantle an Atomic Bomb |
E23024
|
entity |
| Predicate | recordedInTimePeriod |
P17404
|
FINISHED |
| Object | 2003–2004 |
—
|
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–2004 | Statement: [How to Dismantle an Atomic Bomb, recordedInTimePeriod, 2003–2004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recordedInTimePeriod Context triple: [How to Dismantle an Atomic Bomb, recordedInTimePeriod, 2003–2004]
-
A.
livedDuring
Indicates that the subject existed or was alive at some point within the time period or lifespan associated with the object.
-
B.
compiledInPeriod
chosen
Indicates that the creation or compilation of something occurred within a specified time period.
-
C.
historicallyRecordedSince
Indicates that the existence, occurrence, or recognition of one entity has been documented in historical records starting from the time specified by another entity.
-
D.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
E.
timePeriodCoveredTo
Indicates the span or duration of time that is encompassed, addressed, or relevant to a given subject or entity.
- 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_69a493ec75988190b63a11bafaec29b4 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc4bc21881909dcfe628f59f3e8c |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb48de2081909a0dce005b1c9df1 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.