Triple
T27397700
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-56 |
E691735
|
entity |
| Predicate | freeFlyerDeployed |
P12960
|
FINISHED |
| Object | SPARTAN-201 |
—
|
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: SPARTAN-201 | Statement: [STS-56, freeFlyerDeployed, SPARTAN-201]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeFlyerDeployed Context triple: [STS-56, freeFlyerDeployed, SPARTAN-201]
-
A.
foreignDeployment
Indicates that an entity is deployed or stationed outside its own country or usual national territory.
-
B.
hasFlySystem
Indicates that one entity (typically a venue or stage) is equipped with a fly system for lifting, lowering, and suspending scenery, lighting, or other stage elements.
-
C.
deployedTo
chosen
Indicates that something (such as a resource, application, or unit) has been placed, installed, or made operational in a specific target environment or location.
-
D.
deploys
Indicates the action of strategically placing or releasing something into operation or use, often in a specific context or location.
-
E.
flybyAgency
Indicates the agency or organization responsible for conducting or managing a spacecraft’s flyby of a target body.
- 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_69ef5204f7048190bf226a129858fc5b |
completed | April 27, 2026, 12:09 p.m. |
| NER | Named-entity recognition | batch_69f62cb1619481909e4f7391df3c6837 |
completed | May 2, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69f623aaf40081909f947431424a1d55 |
completed | May 2, 2026, 4:17 p.m. |
Created at: April 27, 2026, 12:28 p.m.