Triple
T26394656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GLEEP research reactor |
E663514
|
entity |
| Predicate | firstCriticalityYear |
P18502
|
FINISHED |
| Object | 1947 |
—
|
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: 1947 | Statement: [GLEEP research reactor, firstCriticalityYear, 1947]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCriticalityYear Context triple: [GLEEP research reactor, firstCriticalityYear, 1947]
-
A.
dateOfFirstCriticality
chosen
Indicates the date on which a nuclear reactor or system first achieved a self-sustaining nuclear chain reaction (first became critical).
-
B.
firstCriticalityUnit1
Indicates that the entity is associated with the first unit or level of criticality, specifically labeled as "unit 1."
-
C.
firstCriticalityUnit2
Indicates that the referenced entity is the second unit or component associated with the first level or category of criticality.
-
D.
firstReportedYear
Indicates the year in which something was initially reported, documented, or made known for the first time.
-
E.
firstPermanentBaseYear
Indicates the year in which an entity’s first permanent base or facility was initially established.
- 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_69ee883823988190b418b111be28a44a |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 26, 2026, 11:28 p.m.