Triple
T25750946
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NASA TEMPO |
E648466
|
entity |
| Predicate | hostedPayload |
P34490
|
FINISHED |
| Object | commercial communications satellite |
—
|
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: commercial communications satellite | Statement: [NASA TEMPO, hostedPayload, commercial communications satellite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostedPayload Context triple: [NASA TEMPO, hostedPayload, commercial communications satellite]
-
A.
usesPayload
Indicates that one entity employs or utilizes another entity as its payload in performing an action or function.
-
B.
guestHosted
Indicates that one entity temporarily hosted or presented an event, show, or program in place of or alongside the usual host.
-
C.
hosted
Indicates that one entity organized and provided the venue or platform for an event, activity, or presence involving another entity.
-
D.
hostedAfter
Indicates that one hosting event occurred later in time than another hosting event.
-
E.
secondaryPayload
chosen
Indicates that an entity serves as an additional or subordinate payload associated with a primary payload in an action or relationship.
- 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_69e7ab314d788190b3abe19e114080e1 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6135293908190809e255bf6334760 |
completed | May 2, 2026, 3:08 p.m. |
| PD | Predicate disambiguation | batch_69f611a72780819082f44e66ca2c6ac9 |
completed | May 2, 2026, 3 p.m. |
Created at: April 22, 2026, 4:35 a.m.