Triple
T17089883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rover Environmental Monitoring Station |
E414694
|
entity |
| Predicate | collectsDataFrequency |
P116059
|
FINISHED |
| Object | multiple times per Martian sol |
—
|
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: multiple times per Martian sol | Statement: [Rover Environmental Monitoring Station, collectsDataFrequency, multiple times per Martian sol]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collectsDataFrequency Context triple: [Rover Environmental Monitoring Station, collectsDataFrequency, multiple times per Martian sol]
-
A.
measurementFrequency
Indicates how often a measurement is taken or recorded over time.
-
B.
serviceFrequencyType
Indicates how often a service occurs or is scheduled within a given time period.
-
C.
collectsDataFor
Indicates that one entity gathers or records data on behalf of, or for the benefit of, another entity.
-
D.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
E.
telemetryFrequency
chosen
Indicates how often telemetry data is collected, transmitted, or reported over time.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbf948d88190a4dd4a0774a8505b |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d67b14481909fcdbdeaa5c34785 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:35 a.m.