Triple
T719319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chicago Pile-1 |
E14380
|
entity |
| Predicate | dateOfFirstCriticality |
P18502
|
FINISHED |
| Object | 1942-12-02 |
—
|
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: 1942-12-02 | Statement: [Chicago Pile-1, dateOfFirstCriticality, 1942-12-02]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstCriticality Context triple: [Chicago Pile-1, dateOfFirstCriticality, 1942-12-02]
-
A.
immediateCauseDate
Indicates the specific date on which an event or condition directly caused another event or outcome to occur.
-
B.
firstRaisedAt
Indicates the initial time or context at which an issue, topic, or matter was first brought up or introduced.
-
C.
firstCreatedAt
Indicates the time or date at which an entity was initially created for the first time.
-
D.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
E.
createdAt
Indicates the date and time at which an entity was initially created or came into existence.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f513608190b716b939d574c292 |
completed | March 1, 2026, 8:43 p.m. |
| PDg | Predicate description generation | batch_69a4a57267c481909790a1fda3fced08 |
completed | March 1, 2026, 8:45 p.m. |
Created at: March 1, 2026, 7:37 p.m.