Triple
T19516591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Victoria Crater |
E488291
|
entity |
| Predicate | hasRoleInMission |
P45245
|
FINISHED |
| Object | primary science target for Opportunity extended mission |
—
|
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: primary science target for Opportunity extended mission | Statement: [Victoria Crater, hasRoleInMission, primary science target for Opportunity extended mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRoleInMission Context triple: [Victoria Crater, hasRoleInMission, primary science target for Opportunity extended mission]
-
A.
roleInMissions
chosen
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
B.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
C.
hasMissionIn
Indicates that an entity carries out, undertakes, or is assigned a mission within a specified location or region.
-
D.
containsMission
Indicates that one entity includes or encompasses a mission as part of its contents, scope, or responsibilities.
-
E.
selectedForMission
Indicates that an entity has been chosen or assigned to participate in a particular mission.
- 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_69d8e8da8bec819081f400199491ccc3 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6359ca7648190804c4d655170fda3 |
completed | April 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7d0da88190aabf8b5799691fb1 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.