Triple
T20599174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mir EO-22 |
E506127
|
entity |
| Predicate | crewPresence |
P102598
|
FINISHED |
| Object | continuous human presence on Mir |
—
|
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: continuous human presence on Mir | Statement: [Mir EO-22, crewPresence, continuous human presence on Mir]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewPresence Context triple: [Mir EO-22, crewPresence, continuous human presence on Mir]
-
A.
crewOnboard
Indicates that a person or group is serving as crew aboard a specific vehicle, vessel, or craft.
-
B.
crewInvolvedIn
Indicates that a crew (as a group or unit) participates in, contributes to, or is otherwise involved in a specified event, activity, or operation.
-
C.
crewStatus
Indicates the current operational or role-related condition of a crew member or crew group within a mission or organization.
-
D.
crewRequired
Indicates that a certain number or type of crew members is necessary to operate or support the associated entity or activity.
-
E.
scenePresence
chosen
Indicates that an entity is present or appears within a particular scene or context.
- 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_69e0b4ba6ae88190af871e1f9522c704 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6aa1e251c8190926dafe1402eb63c |
completed | April 20, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69e59fffe1748190825e4eaa90340631 |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:40 a.m.