Triple
T6444942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury-Atlas 7 |
E138317
|
entity |
| Predicate | crewLandingStatus |
P70692
|
FINISHED |
| Object | astronaut recovered 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: astronaut recovered safely | Statement: [Mercury-Atlas 7, crewLandingStatus, astronaut recovered safely]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewLandingStatus Context triple: [Mercury-Atlas 7, crewLandingStatus, astronaut recovered safely]
-
A.
crewLandingDuration
Indicates the length of time a crewed mission spends on the surface after landing before departure or ascent.
-
B.
lastCrewedLandingDate
Indicates the calendar date on which the most recent crewed landing associated with the subject took place.
-
C.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
D.
hasLandingConditions
Indicates the specific conditions or requirements that must be met for a landing to occur or be permitted.
-
E.
crewStatus
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
- 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_69c008aa61ac8190bc96715ed79fe2d8 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c0698d866c81909ef3e0a53833ff7d |
completed | March 22, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69c060faaf248190bbdc8ff909c8777a |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623e3cd48190929b0e3cba013909 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:46 p.m.