Triple
T1866084
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | X-10 graphite reactor |
E34923
|
entity |
| Predicate | firstFullPowerOperationDate |
P13819
|
FINISHED |
| Object | 1943-11 |
—
|
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: 1943-11 | Statement: [X-10 graphite reactor, firstFullPowerOperationDate, 1943-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFullPowerOperationDate Context triple: [X-10 graphite reactor, firstFullPowerOperationDate, 1943-11]
-
A.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstOperationalUse
chosen
Indicates the point in time or context when something is used operationally for the very first time.
-
C.
firstUsedOn
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
D.
firstProducedAt
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
E.
firstYearOfUse
Indicates the year in which something was first put into use or began being used.
- 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_69a88600b2f88190bc09303e68ab517e |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69abb16c09e48190a345c95eab59fd87 |
completed | March 7, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69abafe02c3c819093a4744b476106ca |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:34 p.m.