Triple
T11181085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Ignition Facility |
E264537
|
entity |
| Predicate | researchApplication |
P83724
|
FINISHED |
| Object | nuclear weapons physics |
—
|
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: nuclear weapons physics | Statement: [National Ignition Facility, researchApplication, nuclear weapons physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchApplication Context triple: [National Ignition Facility, researchApplication, nuclear weapons physics]
-
A.
researchArm
Indicates that an entity is a specific study group or treatment arm within a research or clinical trial design.
-
B.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
C.
appliesResearchTo
chosen
Indicates that an entity uses or implements research findings, methods, or insights in relation to another entity, context, or problem.
-
D.
researchProgram
Indicates that an entity is engaged in, associated with, or part of a structured research initiative or program.
-
E.
researchModel
Indicates that an entity systematically investigates, develops, or analyzes a model as part of a research process.
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a7f35481909f35feb94ef10e80 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf4461c8190af84060f7db83211 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.