Triple
T26990381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | systems command |
E679847
|
entity |
| Predicate | lifeCyclePhase |
P31531
|
FINISHED |
| Object | disposal and demilitarization |
—
|
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: disposal and demilitarization | Statement: [systems command, lifeCyclePhase, disposal and demilitarization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeCyclePhase Context triple: [systems command, lifeCyclePhase, disposal and demilitarization]
-
A.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
B.
lifeCycleStructure
Indicates the structural pattern or organization of stages and transitions that make up an entity’s life cycle.
-
C.
lifeCycleEvent
Indicates an event or transition occurring at a particular stage within an entity's overall life cycle.
-
D.
lifecycleStatus
chosen
Indicates the current phase or condition of an entity within its overall lifecycle or progression from creation to termination.
-
E.
lifeCycleRole
Indicates the role an entity plays within a defined life cycle or process stage, such as its function or status at that point in the sequence.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c663be481908f233d25d28713a4 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:51 a.m.