Triple
T25643334
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NS-16 mission |
E642889
|
entity |
| Predicate | crewRoleOfWallyFunk |
P159477
|
FINISHED |
| Object | Mercury 13 member |
—
|
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: Mercury 13 member | Statement: [NS-16 mission, crewRoleOfWallyFunk, Mercury 13 member]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewRoleOfWallyFunk Context triple: [NS-16 mission, crewRoleOfWallyFunk, Mercury 13 member]
-
A.
crewRoleOfWallyFunk
chosen
Indicates the specific crew role or position that Wally Funk holds within a spaceflight or mission crew.
-
B.
crewRoleOfHelenSharman
Indicates the specific crew role or position that Helen Sharman held within a space mission or crew.
-
C.
crewRoleOf_Valentina Tereshkova
Indicates that a specified crew role is held by, or associated with, Valentina Tereshkova within a particular mission or context.
-
D.
crewRole_HelenSharman
Indicates the specific role or position that Helen Sharman holds or held as a member of a crew.
-
E.
crewRoleOf Wally Schirra
Indicates the specific crew position or function that Wally Schirra held within a particular mission or spacecraft crew.
- 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_69e77e7ce28081908b08d65ee6e5c8be |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f5faa22e7c81908af7fe96952bebe0 |
completed | May 2, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69f5afec3e94819080d9ba86cf8c866e |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 5:48 p.m.