Triple
T11090883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-36 |
E262248
|
entity |
| Predicate | crewSurvival |
P24303
|
FINISHED |
| Object | all crew returned safely |
—
|
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: all crew returned safely | Statement: [STS-36, crewSurvival, all crew returned safely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewSurvival Context triple: [STS-36, crewSurvival, all crew returned safely]
-
A.
survivesShipwreck
Indicates that an entity continues to live or remain alive after experiencing a shipwreck.
-
B.
helpsSurvive
Indicates that one entity provides support or advantage that increases another entity’s chances of survival.
-
C.
crewLifeSupportCapability
Indicates the ability of a system or vehicle to provide and maintain necessary life support functions for its crew.
-
D.
crewSurvivorsOnReturn
chosen
Indicates that the members of a crew remained alive and successfully returned from a mission or journey.
-
E.
survivingFrom
Indicates that one entity continues to live, exist, or remain after another related entity has ended, disappeared, or ceased to exist.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d799ebae8c8190987b474adb7ede47 |
completed | April 9, 2026, 12:22 p.m. |
| PD | Predicate disambiguation | batch_69d744185a5881909ba4cf151d1798ec |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:27 p.m.