Triple
T19382253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eagle Crater |
E484839
|
entity |
| Predicate | missionPhaseRole |
P45245
|
FINISHED |
| Object | initial landing and checkout site for Opportunity |
—
|
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: initial landing and checkout site for Opportunity | Statement: [Eagle Crater, missionPhaseRole, initial landing and checkout site for Opportunity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionPhaseRole Context triple: [Eagle Crater, missionPhaseRole, initial landing and checkout site for Opportunity]
-
A.
missionPhaseAfter
Indicates that one mission phase occurs later in sequence or time than another mission phase.
-
B.
roleInMissions
chosen
Indicates the specific function, duty, or position an entity holds within one or more missions.
-
C.
missionPhaseTested
Indicates that a specific mission phase has been evaluated or validated through testing.
-
D.
militaryRole
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
E.
missionProfile
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a614cf88190b561eafaa350ce19 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.