Triple
T27881153
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-41-C |
E705092
|
entity |
| Predicate | satelliteDeployed |
P32888
|
FINISHED |
| Object | Long Duration Exposure Facility |
—
|
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: Long Duration Exposure Facility | Statement: [STS-41-C, satelliteDeployed, Long Duration Exposure Facility]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: satelliteDeployed Context triple: [STS-41-C, satelliteDeployed, Long Duration Exposure Facility]
-
A.
deployedSatellite
chosen
Indicates that one entity has placed another entity into orbit or operational status as a satellite.
-
B.
developedSatellite
Indicates that one entity was responsible for creating, engineering, or building a particular satellite.
-
C.
plannedSatellites
Indicates that certain satellites are intended or scheduled to be launched, deployed, or put into operation in association with a given entity or context.
-
D.
satellite
Indicates that one entity orbits and is gravitationally bound to another, typically larger, central body.
-
E.
retrievedSatellite
Indicates that an entity has successfully recovered or brought back a satellite from a prior location or state.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63982891c8190b29054f8c0276342 |
completed | May 2, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69f6318be69481909d1bcf29b7b60eb2 |
completed | May 2, 2026, 5:17 p.m. |
Created at: April 27, 2026, 6:30 p.m.