Triple
T4800017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kansas City National Security Campus |
E106808
|
entity |
| Predicate | typeOfComponents |
P6678
|
FINISHED |
| Object | non-nuclear weapon components |
—
|
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: non-nuclear weapon components | Statement: [Kansas City National Security Campus, typeOfComponents, non-nuclear weapon components]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfComponents Context triple: [Kansas City National Security Campus, typeOfComponents, non-nuclear weapon components]
-
A.
componentType
chosen
Indicates that one entity specifies or classifies the kind or category of component that another entity represents or uses.
-
B.
typicalComponent
Indicates that one entity is a standard or representative component or part of another entity.
-
C.
componentFrom
Indicates that one entity is derived from, produced by, or originates as a component of another entity.
-
D.
componentsDefinition
Indicates that one entity defines or specifies the components that make up another entity.
-
E.
dimensionOfComponents
Indicates that a specified dimension value is associated with, or applies to, the components of an object or system.
- 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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:23 p.m.