Triple
T27397701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-56 |
E691735
|
entity |
| Predicate | freeFlyerOperation |
P162654
|
FINISHED |
| Object | solar wind and corona observations |
—
|
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: solar wind and corona observations | Statement: [STS-56, freeFlyerOperation, solar wind and corona observations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: freeFlyerOperation Context triple: [STS-56, freeFlyerOperation, solar wind and corona observations]
-
A.
flightOver
Indicates that one entity moves through the air above or across another entity or area.
-
B.
flightStyle
Indicates the characteristic manner or pattern in which an entity performs or exhibits flight.
-
C.
flybyAgency
Indicates the agency or organization responsible for conducting or managing a spacecraft’s flyby of a target body.
-
D.
firstFlightService
Indicates that an entity operates or provides service on the earliest scheduled flight in a given context or route.
-
E.
testFlightCenter
Indicates that an entity serves as a center or facility where test flights are conducted or managed.
- 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_69f62d89b89c8190afb372a8172111e7 |
completed | May 2, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69f62c1762f881908c25e8f70ecd5041 |
completed | May 2, 2026, 4:53 p.m. |
| PDg | Predicate description generation | batch_69f62cd1912c8190ab3f3288442115a4 |
completed | May 2, 2026, 4:56 p.m. |
Created at: April 27, 2026, 12:28 p.m.