Triple
T33940269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Voyager 1 electrical power subsystem |
E870144
|
entity |
| Predicate | cannotUse |
P17604
|
FINISHED |
| Object | solar arrays |
—
|
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: solar arrays | Statement: [Voyager 1 electrical power subsystem, cannotUse, solar arrays]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cannotUse Context triple: [Voyager 1 electrical power subsystem, cannotUse, solar arrays]
-
A.
cannot
chosen
Indicates that one entity lacks the ability, permission, or possibility to perform an action or participate in a specified relationship with another entity.
-
B.
cannotBeUsedWithout
Indicates that one entity is dependent on another such that it cannot function, operate, or be utilized unless the other entity is also present or in use.
-
C.
cannotShow
Indicates that one entity is unable or not permitted to display, reveal, or present another entity.
-
D.
cannotGrant
Indicates that an entity lacks the authority, permission, or ability to confer a requested right, access, or resource to another entity.
-
E.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
- 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_69f3499b0dd48190b07b4b60babcee02 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7064e906881909c3186c646145d34 |
completed | May 3, 2026, 8:24 a.m. |
| PD | Predicate disambiguation | batch_69f70100ec1c8190a6b97f50e88891f2 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:49 a.m.