Triple
T4994070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opportunity |
E112200
|
entity |
| Predicate | communicationWithEarth |
P2798
|
FINISHED |
| Object | via Deep Space Network |
—
|
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: via Deep Space Network | Statement: [Opportunity, communicationWithEarth, via Deep Space Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationWithEarth Context triple: [Opportunity, communicationWithEarth, via Deep Space Network]
-
A.
hostSpaceAgency
Indicates that one entity serves as the space agency that organizes, manages, or officially represents space-related activities for another entity (such as a mission, event, or facility).
-
B.
communicatesTo
Indicates that one entity sends or conveys information, messages, or signals to another entity as the intended recipient.
-
C.
communicationChannel
chosen
Indicates a medium or method through which information is transmitted between parties.
-
D.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
E.
forEarthApprox
Indicates an approximate or estimated value or condition as it pertains to Earth or an Earth-related context.
- 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_69bd4432b32c81909f3b3c6bd10f0653 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74249a8c8190952680aee06a9286 |
completed | March 20, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69bd71492dec8190af4c27a3043b35cc |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:34 p.m.