Triple
T16496680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kosmos-3M |
E400700
|
entity |
| Predicate | typicalPayloadClass |
P8440
|
FINISHED |
| Object | small satellites |
—
|
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: small satellites | Statement: [Kosmos-3M, typicalPayloadClass, small satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalPayloadClass Context triple: [Kosmos-3M, typicalPayloadClass, small satellites]
-
A.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
retrievedPayload
Indicates that an entity has successfully obtained and brought back a specified payload from a source or operation.
-
C.
plannedPayload
Indicates that an entity is designated or scheduled to be carried, delivered, or transported as part of a planned operation or mission.
-
D.
isKeyPayloadOf
Indicates that something functions as the primary or essential data component (key payload) within another entity or structure.
-
E.
hasPayloadStructure
Indicates that an entity is associated with, or characterized by, a specific structure or organization of its payload.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e343a7c81909e04cbaaa40e2531 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
Created at: April 10, 2026, 5:14 a.m.