Triple
T17130904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JunoCam |
E415717
|
entity |
| Predicate | actualOperation |
P5667
|
FINISHED |
| Object | extended beyond original design lifetime |
—
|
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: extended beyond original design lifetime | Statement: [JunoCam, actualOperation, extended beyond original design lifetime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualOperation Context triple: [JunoCam, actualOperation, extended beyond original design lifetime]
-
A.
operationOf
Indicates that one entity is the function, activity, or process carried out by another entity (such as a system, device, or organization).
-
B.
performsOperation
Indicates that one entity carries out or executes a specific operation on or for another entity.
-
C.
primaryOperation
Indicates the main or most important operation performed or used by an entity in a given context.
-
D.
inOperation
Indicates that an entity (such as a system, device, or facility) is currently active, functioning, and performing its intended operation.
-
E.
associatedOperation
chosen
Indicates that one entity is linked to or involved with a particular operation, process, or activity.
- 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f029d1a48190a9d4094827d11d23 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.