Triple
T27881155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-41-C |
E705092
|
entity |
| Predicate | satelliteServiced |
P163746
|
FINISHED |
| Object | SolarMax |
E1490797
|
NE 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: SolarMax | Statement: [STS-41-C, satelliteServiced, SolarMax]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteServiced Context triple: [STS-41-C, satelliteServiced, SolarMax]
-
A.
satelliteServiced
chosen
Indicates that a satellite has received maintenance, repair, or operational support services from another entity.
-
B.
satelliteService
Indicates a relationship where one entity provides or supports satellite-based services or operations for another entity.
-
C.
hasSatelliteStatus
Indicates that one entity holds the status of being a satellite (e.g., dependent, subordinate, or orbiting body) in relation to another entity.
-
D.
satellite
Indicates that one entity orbits and is gravitationally bound to another, typically larger, central body.
-
E.
operatesOnSatellite
Indicates that an entity performs operations or exercises control over a satellite.
- F. None of above.
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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a130354f838819083a25289cb1d64fa |
completed | May 24, 2026, 1:55 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:30 p.m.