Triple
T5561245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LORRI |
E145769
|
entity |
| Predicate | missionPhaseUsage |
P59737
|
FINISHED |
| Object | cruise phase imaging |
—
|
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: cruise phase imaging | Statement: [LORRI, missionPhaseUsage, cruise phase imaging]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPhaseUsage Context triple: [LORRI, missionPhaseUsage, cruise phase imaging]
-
A.
supportsMissionPhase
Indicates that one entity provides the necessary capabilities, resources, or conditions for another entity to function or be valid during a specific mission phase.
-
B.
targetsPhase
chosen
Indicates that an action, process, or entity is specifically directed toward or intended to affect a particular phase or stage within a larger sequence or lifecycle.
-
C.
usedByMission
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of a particular mission.
-
D.
currentMissionPhase
Indicates the specific phase or stage that a mission is presently in within its overall lifecycle.
-
E.
missionCadence
Indicates the frequency or regular interval at which missions are planned, launched, or conducted.
- 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_69c008fcaf788190bafa02a1917ee73b |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02019c6748190aeefb86f489f726a |
completed | March 22, 2026, 5 p.m. |
| PD | Predicate disambiguation | batch_69c01b10bbf8819098655839c03b7832 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:36 p.m.