Triple
T4065168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ingenuity helicopter |
E86306
|
entity |
| Predicate | actualMissionDurationDays |
P40756
|
FINISHED |
| Object | over 1000 |
—
|
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: over 1000 | Statement: [Ingenuity helicopter, actualMissionDurationDays, over 1000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: actualMissionDurationDays Context triple: [Ingenuity helicopter, actualMissionDurationDays, over 1000]
-
A.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
B.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
C.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
D.
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.
-
E.
typicalDurationDays
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
- 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_69aed93c69208190a4efac0efe3cd69b |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefd0bdea48190805a79515ee92709 |
completed | March 9, 2026, 5:02 p.m. |
| PD | Predicate disambiguation | batch_69aef90438908190a005b08ba271eacf |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:38 p.m.