Triple
T9240946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SS-18 Satan |
E222055
|
entity |
| Predicate | enteredRussianService |
P86744
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [SS-18 Satan, enteredRussianService, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enteredRussianService Context triple: [SS-18 Satan, enteredRussianService, 1990s]
-
A.
enteredService
Indicates that an entity began active use or operation at a specific time or in a specific context.
-
B.
enteredServiceWithUnit
Indicates that an entity began its period of service or active duty while assigned to a specified unit.
-
C.
enteredServiceAsReplacementFor
Indicates that one entity began its period of service specifically to take over the role or function previously performed by another entity.
-
D.
enteredServiceWithOperator
chosen
Indicates that an entity began operational service under the responsibility or control of a specified operator.
-
E.
enteredServiceAsCS100
Indicates that an entity began operational service specifically in the configuration or role designated as CS100.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf0a3888c8190b72d8d0b850bdfbc |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.