Triple
T33133534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NROL-44 |
E847937
|
entity |
| Predicate | spacecraftOwner |
P80639
|
FINISHED |
| Object | United States government |
—
|
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: United States government | Statement: [NROL-44, spacecraftOwner, United States government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spacecraftOwner Context triple: [NROL-44, spacecraftOwner, United States government]
-
A.
satelliteOwner
chosen
Indicates that one entity is the legal or recognized owner of a particular satellite.
-
B.
hostSpacecraftOperator
Indicates that one entity operates or manages the spacecraft that is being hosted or carried by another entity.
-
C.
relatedSpacecraft
Indicates that there is an association or connection between two spacecraft, such as shared mission, design, origin, or operational relationship.
-
D.
mentionsSpacecraft
Indicates that one entity makes reference to or discusses a particular spacecraft.
-
E.
spacecraftDeveloper
Indicates that one entity is the organization or individual responsible for designing, building, or developing the spacecraft represented by the other entity.
- 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_69f3495961d88190b16ea542c2c5f825 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:27 a.m.