Triple
T19298392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhurong rover |
E482626
|
entity |
| Predicate | actualOperationDuration |
P40756
|
FINISHED |
| Object | More than 1 Earth year |
—
|
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: More than 1 Earth year | Statement: [Zhurong rover, actualOperationDuration, More than 1 Earth year]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualOperationDuration Context triple: [Zhurong rover, actualOperationDuration, More than 1 Earth year]
-
A.
actualDuration
chosen
Indicates the real amount of time that an event, process, or activity actually took to complete, as opposed to its planned or estimated duration.
-
B.
surfaceOperationsDuration
Indicates the length of time that surface-related operations or activities are carried out.
-
C.
durationTotal
Indicates the overall length of time for which an event, process, or state persists, typically aggregating all its constituent durations.
-
D.
intendedDuration
Indicates the planned or expected length of time for which an action, event, or state is meant to occur or remain in effect.
-
E.
inOperationDuring
Indicates that an entity is actively functioning or in use throughout a specified time period or event.
- 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc86f8648190920d122bb141c6e5 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.