Triple
T743163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gadget |
E15286
|
entity |
| Predicate | safetyTesting |
P17991
|
FINISHED |
| Object | preceded by non-nuclear implosion tests |
—
|
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: preceded by non-nuclear implosion tests | Statement: [The Gadget, safetyTesting, preceded by non-nuclear implosion tests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: safetyTesting Context triple: [The Gadget, safetyTesting, preceded by non-nuclear implosion tests]
-
A.
safety
Indicates that an entity provides, ensures, or is associated with protection from harm, danger, or risk for another entity or within a given context.
-
B.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
C.
hasSafetyRegulationCompliance
Indicates that an entity adheres to, satisfies, or is in conformity with specified safety regulations or standards.
-
D.
appliedTest
chosen
Indicates that a test has been administered or carried out on a particular subject or object.
-
E.
testsIn
Indicates that one entity conducts or performs tests within, on, or using another entity.
- 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_69a49358aa308190adbc9b5a0a2adcf9 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a60f92d08190a4f44c5b4d068ab5 |
completed | March 1, 2026, 8:48 p.m. |
| PD | Predicate disambiguation | batch_69a4a4fdaaf48190985f62acfc069508 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.