Triple
T32394021
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-70 |
E827752
|
entity |
| Predicate | TDRSSOrbitalSlot |
P174885
|
FINISHED |
| Object | TDRS-7 (TDRS-G) in geosynchronous orbit |
—
|
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: TDRS-7 (TDRS-G) in geosynchronous orbit | Statement: [STS-70, TDRSSOrbitalSlot, TDRS-7 (TDRS-G) in geosynchronous orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TDRSSOrbitalSlot Context triple: [STS-70, TDRSSOrbitalSlot, TDRS-7 (TDRS-G) in geosynchronous orbit]
-
A.
TDRSseries
Indicates that one entity is part of, or associated with, the Tracking and Data Relay Satellite (TDRS) series of satellites or missions.
-
B.
spaceStationOrbit
Indicates that a space station is in orbit around a specified celestial body or location.
-
C.
deployedSatellite
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
D.
satelliteDesignation
Indicates that one entity is designated or classified as a satellite of another entity.
-
E.
spaceStationAssociation
Indicates an affiliation or operational relationship between an entity and a specific space station, such as ownership, management, use, or service connection.
- 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_69f349184e7481909c6c54428cb9cf12 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 12:52 a.m.