Triple
T16431841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mars Sample Return campaign |
E399086
|
entity |
| Predicate | includesMissionElement |
P53282
|
FINISHED |
| Object | sample collection rover |
—
|
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: sample collection rover | Statement: [Mars Sample Return campaign, includesMissionElement, sample collection rover]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesMissionElement Context triple: [Mars Sample Return campaign, includesMissionElement, sample collection rover]
-
A.
hasMissionSystem
Indicates that an entity is equipped with or associated with a specific mission-related system or subsystem.
-
B.
exampleMission
Indicates that one entity serves as a representative or illustrative mission associated with another entity.
-
C.
isTargetOfMission
Indicates that an entity is the intended objective or focus of a particular mission or operation.
-
D.
capturesMissionOf
Indicates that one entity records, represents, or encapsulates the mission or overarching purpose of another entity.
-
E.
usedByMission
chosen
Indicates that something (such as a resource, tool, or method) is utilized or employed in the execution of 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9dffe48190a23852f828af55d8 |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.