Triple
T15221163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EELV program |
E363767
|
entity |
| Predicate | servedPayloadType |
P8440
|
FINISHED |
| Object | military communications 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: military communications satellites | Statement: [EELV program, servedPayloadType, military communications satellites]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedPayloadType Context triple: [EELV program, servedPayloadType, military communications satellites]
-
A.
payloadType
chosen
Indicates the kind or category of payload associated with or carried by an entity or action.
-
B.
payloadServiced
Indicates that a payload has been attended to, maintained, or otherwise handled to fulfill its required service or operational needs.
-
C.
servedLineType
Indicates the type or category of service line associated with or provided in a given context.
-
D.
servesDestinationType
Indicates that an entity provides service to, or is intended for use with, a specific type or category of destination.
-
E.
servedWith
Indicates that one item is customarily presented, provided, or consumed together with another as an accompaniment or side.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00788b04881909dad9b346ce3b4a9 |
completed | April 15, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69deca8479188190b2e5d3bc708d7d07 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:12 a.m.