Triple
T33940121
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FDS |
E870141
|
entity |
| Predicate | communicationPartner |
P69005
|
FINISHED |
| Object | NASA Deep Space Network |
—
|
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: NASA Deep Space Network | Statement: [FDS, communicationPartner, NASA Deep Space Network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationPartner Context triple: [FDS, communicationPartner, NASA Deep Space Network]
-
A.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
communicationService
chosen
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
-
C.
communicationChannel
Indicates a medium or method through which information is transmitted between parties.
-
D.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
E.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:49 a.m.