Triple
T21461741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molniya communications satellites |
E529487
|
entity |
| Predicate | typicalOperationalLifetime |
P70126
|
FINISHED |
| Object | several years |
—
|
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: several years | Statement: [Molniya communications satellites, typicalOperationalLifetime, several years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalOperationalLifetime Context triple: [Molniya communications satellites, typicalOperationalLifetime, several years]
-
A.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
B.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
C.
hasTypicalUseTime
chosen
Indicates the usual or expected duration or time period during which something is commonly used or in operation.
-
D.
typicalUseDays
Indicates the usual or expected number of days over which something is used or intended to be used.
-
E.
serviceLifeTarget
Indicates the intended or planned duration of time that a service, asset, or component is expected to remain in use or perform its function.
- 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_69e0c458133481908ae8b41a12c4edec |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69e9e9ef0c0881908554977df00604a6 |
completed | April 23, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69e631df1b38819088d3604854e697b4 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:09 p.m.