Triple
T27396265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-55 |
E691695
|
entity |
| Predicate | SpacelabSponsor |
P167123
|
FINISHED |
| Object | German Aerospace Center DLR |
—
|
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: German Aerospace Center DLR | Statement: [STS-55, SpacelabSponsor, German Aerospace Center DLR]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SpacelabSponsor Context triple: [STS-55, SpacelabSponsor, German Aerospace Center DLR]
-
A.
spacelabSeries
Indicates that one entity is part of, or belongs to, a particular series of Spacelab missions or modules.
-
B.
carriedSpacelab
Indicates that one entity transported or bore the Spacelab module, typically as payload, during a mission or operation.
-
C.
spacelabModuleType
Indicates the specific functional type or classification assigned to a given Spacelab module.
-
D.
spaceAgencyCustomer
Indicates a relationship where one entity is a customer that purchases or contracts services from a space agency.
-
E.
coordinatesSpaceProgramsFor
Indicates that one entity organizes, manages, or aligns the space program activities or initiatives of another entity.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 27, 2026, 12:27 p.m.