Triple
T7158477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-61-C |
E166875
|
entity |
| Predicate | launchDelaysReason |
P61105
|
FINISHED |
| Object | weather |
—
|
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: weather | Statement: [STS-61-C, launchDelaysReason, weather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDelaysReason Context triple: [STS-61-C, launchDelaysReason, weather]
-
A.
delayedBy
chosen
Indicates that one event, process, or action occurs later than expected or planned due to the influence or interference of another factor or entity.
-
B.
launchStatus
Indicates the current state or phase of a launch process, such as whether it is planned, in progress, successful, or failed.
-
C.
launchPeriod
Indicates the time span during which a launch or deployment activity occurs or is valid.
-
D.
launchFailures
Indicates that attempts to initiate or start an operation, process, or system have failed.
-
E.
launchOutcome
Indicates the result or consequence of a launch event, such as whether it succeeded, failed, or had a specific status or outcome.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e8109a64819087e132d6d483c07d |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.