Triple
T22201491
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MR-3 |
E548694
|
entity |
| Predicate | crewEgress |
P91753
|
FINISHED |
| Object | recovered at sea after splashdown |
—
|
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: recovered at sea after splashdown | Statement: [MR-3, crewEgress, recovered at sea after splashdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewEgress Context triple: [MR-3, crewEgress, recovered at sea after splashdown]
-
A.
crewIngressEgress
chosen
Indicates the process by which crew members enter into or exit from a vehicle, facility, or designated area.
-
B.
crew
Indicates that one entity serves as the group of people who operate, staff, or work on another entity (such as a vehicle, vessel, or production).
-
C.
coCrewMember
Indicates that two or more individuals serve together as members of the same crew on a shared mission, vehicle, or operation.
-
D.
crewCab
Indicates that a vehicle has a crew cab configuration, meaning its cabin is designed to seat multiple occupants in both front and rear rows.
-
E.
crewType
Indicates the specific role or category of crew associated with an entity, such as the type of personnel assigned to operate or support it.
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aeb16348190a34f96b47e01c8cf |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:36 p.m.