Triple
T33080997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DemoSat |
E846506
|
entity |
| Predicate | payloadStatus |
P175781
|
FINISHED |
| Object | non-operational |
—
|
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: non-operational | Statement: [DemoSat, payloadStatus, non-operational]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadStatus Context triple: [DemoSat, payloadStatus, non-operational]
-
A.
payloadServiced
Indicates that a payload has been attended to, maintained, or otherwise handled to fulfill its required service or operational needs.
-
B.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
-
C.
statusTransmission
Indicates that a status or state is being communicated or passed from one entity to another.
-
D.
payloadAction
Indicates an action performed on, with, or involving a payload (such as creating, sending, modifying, or processing it).
-
E.
payloadName
Indicates the specific name assigned to a payload associated with an action, event, or data transfer between entities.
- 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d27120988190aacec621cf2bf0e8 |
completed | May 3, 2026, 4:43 a.m. |
| PDg | Predicate description generation | batch_69f6d6a482fc8190b526291cd99b8696 |
completed | May 3, 2026, 5:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.