Triple
T36828370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Ignition Facility |
E910069
|
entity |
| Predicate | firstFullOperationsDate |
P53435
|
FINISHED |
| Object | around 2009 |
—
|
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: around 2009 | Statement: [National Ignition Facility, firstFullOperationsDate, around 2009]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstFullOperationsDate Context triple: [National Ignition Facility, firstFullOperationsDate, around 2009]
-
A.
fullOperationDate
chosen
Indicates the date on which an operation or process is fully carried out or becomes completely effective.
-
B.
firstIntroductionDate
Indicates the date on which an entity was first introduced or presented for the first time.
-
C.
operatorStartDate
Indicates the date on which an operator’s role, activity, or responsibility begins.
-
D.
initiallyOperated
Indicates that an entity first began functioning, being used, or carrying out its intended operation at a specified initial time or under initial conditions.
-
E.
operatedSince
Indicates that an entity has been in operation continuously from a specified starting time or date.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.