Triple
T30231084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bulletin of the Atomic Scientists |
E768629
|
entity |
| Predicate | DoomsdayClockScale |
P169006
|
FINISHED |
| Object | minutes to midnight |
—
|
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: minutes to midnight | Statement: [Bulletin of the Atomic Scientists, DoomsdayClockScale, minutes to midnight]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DoomsdayClockScale Context triple: [Bulletin of the Atomic Scientists, DoomsdayClockScale, minutes to midnight]
-
A.
DoomsdayClockRepresents
chosen
Indicates that the subject symbolizes or reflects the perceived proximity of humanity to a global catastrophe or existential threat.
-
B.
Doomsday ICoreYears
Indicates a relationship where a doomsday or catastrophic event is associated with, measured in, or scheduled according to specific core years.
-
C.
timePeriodOfMajorDestruction
Indicates the time span during which a major destructive event affecting the subject occurred.
-
D.
timeOfRevelation
Indicates the specific time or moment at which something is revealed or disclosed.
-
E.
timeOfDestruction
Indicates the specific time at which an entity is destroyed or ceases to exist.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f68025551081908f282e9ae3efebe7 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:36 p.m.