Triple
T36906773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M51 SLBM |
E912798
|
entity |
| Predicate | firstOperationalPatrol |
P205631
|
FINISHED |
| Object | 2010 |
—
|
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: 2010 | Statement: [M51 SLBM, firstOperationalPatrol, 2010]
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 (4 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_69f76e879768819085c2fb31a6a5b44b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037cad051c8190b28b354b89208574 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a10036481909c71188b2a0e7f04 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c842b2c819082f1d2db995ac2eb |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:13 p.m.