Triple
T2189168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Computer Command System |
E49820
|
entity |
| Predicate | criticalRole |
P268
|
FINISHED |
| Object | maintaining spacecraft health and safety |
—
|
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: maintaining spacecraft health and safety | Statement: [Computer Command System, criticalRole, maintaining spacecraft health and safety]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: criticalRole Context triple: [Computer Command System, criticalRole, maintaining spacecraft health and safety]
-
A.
criticalReputation
Indicates that an entity is regarded by critics with a particular level or type of esteem, evaluation, or standing based on critical assessments.
-
B.
criticalReception
Indicates how a work, performance, or product is evaluated and responded to by critics or professional reviewers.
-
C.
role
chosen
Indicates the function, position, or responsibility that one entity holds in relation to another within a given context.
-
D.
significantEventRole
Indicates that an entity plays an important or defining role in a particular significant event.
-
E.
deFactoRole
Indicates that an entity effectively functions in a role or capacity in practice, even if that role is not formally or officially assigned.
- 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_69a88aaba3c48190b351cab9b26989ff |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbf9e99f08190892d34485c8f2f25 |
completed | March 7, 2026, 6:03 a.m. |
| PD | Predicate disambiguation | batch_69abbda32d1881909d1fd83a751fb21c |
completed | March 7, 2026, 5:54 a.m. |
Created at: March 4, 2026, 7:46 p.m.