Triple
T5817509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Redstone 3 |
E129022
|
entity |
| Predicate | crewEgressMethod |
P44550
|
FINISHED |
| Object | helicopter recovery from ocean |
—
|
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: helicopter recovery from ocean | Statement: [Mercury-Redstone 3, crewEgressMethod, helicopter recovery from ocean]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewEgressMethod Context triple: [Mercury-Redstone 3, crewEgressMethod, helicopter recovery from ocean]
-
A.
exitsThrough
Indicates that an entity leaves or departs from a place, structure, or area by passing through a specified exit or passage.
-
B.
accessibleExit
Indicates that an exit is designed and configured to be usable by people with disabilities, meeting accessibility requirements.
-
C.
hasEmergencyExits
Indicates that an entity is equipped with designated emergency exits for use during urgent or hazardous situations.
-
D.
crewEscapeCapability
Indicates that an entity has the capability or provision for its crew to escape safely in an emergency situation.
-
E.
evacuationMethod
chosen
Indicates the means or procedure by which people or objects are removed from a place of danger or risk.
- 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_69c0084869e881908d7859492183ca7b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0400f1af881908d376ea4793f6dea |
completed | March 22, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_69c0333fdd7081908d829265caa2ac11 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:53 p.m.