Triple
T30877073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AEHF military communications satellites |
E786506
|
entity |
| Predicate | payloadProvider |
P170593
|
FINISHED |
| Object | Northrop Grumman |
—
|
NE NERFINISHED |
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: Northrop Grumman | Statement: [AEHF military communications satellites, payloadProvider, Northrop Grumman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadProvider Context triple: [AEHF military communications satellites, payloadProvider, Northrop Grumman]
-
A.
payloadModule
Indicates a relationship where a module functions as the payload component within a larger system or structure.
-
B.
payloadField
Indicates that one entity specifies or refers to a particular field within a payload structure associated with another entity.
-
C.
payloadOwner
Indicates that one entity is the owner or controller of a given payload associated with another entity or process.
-
D.
payloadRole
Indicates the functional role or purpose that a payload has within a system, process, or interaction.
-
E.
payloadServiced
Indicates that a payload has been attended to, maintained, or otherwise handled to fulfill its required service or operational needs.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f691d76a808190b24f5a4758a87832 |
completed | May 3, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
| PDg | Predicate description generation | batch_69f68fb914b88190b0cad83ea9fe9dfc |
completed | May 2, 2026, 11:58 p.m. |
Created at: April 29, 2026, 8:48 p.m.