Triple
T32493299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GSAT-5P |
E830447
|
entity |
| Predicate | intendedOperationalLife |
P75499
|
FINISHED |
| Object | about 12 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: about 12 years | Statement: [GSAT-5P, intendedOperationalLife, about 12 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedOperationalLife Context triple: [GSAT-5P, intendedOperationalLife, about 12 years]
-
A.
durationOfUse
Indicates the length of time for which something is used or remains in use.
-
B.
hasMeanLifetime
Indicates the characteristic average time duration for which an entity, state, or condition persists before it decays, ends, or changes.
-
C.
serviceLifeTarget
chosen
Indicates the intended or planned duration of time that a service, asset, or component is expected to remain in use or perform its function.
-
D.
hasLifeSpan
Indicates that an entity is associated with a specific duration or range of time during which it remains alive or exists.
-
E.
lifetimeUse
Indicates that the relationship or action concerns the total or cumulative extent of use of something over the entire duration of an entity’s existence or observation period.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 1, 2026, 12:59 a.m.