Triple
T1639145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-88 |
E35426
|
entity |
| Predicate | EVAobjective |
P30831
|
FINISHED |
| Object | Connect power and data cables between Unity and Zarya |
—
|
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: Connect power and data cables between Unity and Zarya | Statement: [STS-88, EVAobjective, Connect power and data cables between Unity and Zarya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EVAobjective Context triple: [STS-88, EVAobjective, Connect power and data cables between Unity and Zarya]
-
A.
eve
Indicates a relationship where one entity is the evening or night-time counterpart, phase, or occurrence associated with another entity.
-
B.
protectionObjective
Indicates that one entity has the goal or purpose of safeguarding, defending, or preserving another entity or its interests.
-
C.
expeditionObjective
Indicates the primary goal or purpose that an expedition is intended to achieve.
-
D.
opponentObjective
Indicates that one entity is the target or goal that an opposing entity aims to counter, defeat, or prevent from succeeding.
-
E.
trainingObjective
Indicates the goal or target outcome that a training process is designed to achieve.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
| PDg | Predicate description generation | batch_69a9607716b4819092187f8c08daaf31 |
completed | March 5, 2026, 10:52 a.m. |
Created at: March 4, 2026, 7:28 p.m.