Triple
T38539548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Titan 23G |
E924791
|
entity |
| Predicate | usedDecommissionedHardware |
P9772
|
FINISHED |
| Object | Titan II ICBM first stages |
—
|
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: Titan II ICBM first stages | Statement: [Titan 23G, usedDecommissionedHardware, Titan II ICBM first stages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedDecommissionedHardware Context triple: [Titan 23G, usedDecommissionedHardware, Titan II ICBM first stages]
-
A.
decommissionedBy
Indicates that an entity was formally taken out of service or use by a specific agent or authority.
-
B.
usedItem
Indicates that an entity has utilized or employed a particular item for some purpose.
-
C.
usedEquipmentFrom
Indicates that one entity has utilized or operated equipment that originated from or was provided by another entity.
-
D.
decommissionedWith
Indicates that an entity was taken out of service or retired in conjunction with, or as part of the same process as, another specified entity.
-
E.
usedComponent
chosen
Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcdaa36f90819093f8661969990c7d |
completed | May 7, 2026, 6:32 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fefc588190b063d7ea1ec87b07 |
completed | May 7, 2026, 6:25 p.m. |
Created at: May 3, 2026, 4:32 p.m.