Triple
T36906773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M51 SLBM |
E912798
|
entity |
| Predicate | firstOperationalPatrol |
—
|
GENERATED |
| Object | 2010 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstOperationalPatrol Context triple: [M51 SLBM, firstOperationalPatrol, 2010]
-
A.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
B.
firstOperationalCargoMission
Indicates that the subject entity is the earliest or initial cargo mission to be put into operational service for the related program, system, or route.
-
C.
firstCombatOperation
Indicates that the referenced combat operation is the earliest or initial combat action undertaken by the entity in question.
-
D.
firstOperationalCargoMissionDate
Indicates the calendar date on which an entity conducted its first operational mission carrying cargo.
-
E.
firstOperationalMissionUnderContract
Indicates that the mission is the initial operational mission carried out under a specific contract between the involved parties.
- F. None of above. chosen
Provenance (1 batch)
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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.