Triple
T17407990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perseverance |
E423269
|
entity |
| Predicate | terrainNavigation |
P127351
|
FINISHED |
| Object | autonomous hazard avoidance |
—
|
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: autonomous hazard avoidance | Statement: [Perseverance, terrainNavigation, autonomous hazard avoidance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrainNavigation Context triple: [Perseverance, terrainNavigation, autonomous hazard avoidance]
-
A.
terrainIncludes
Indicates that a specified terrain area contains or encompasses another geographic or environmental feature within its boundaries.
-
B.
terrainFeature
Indicates a relationship where one entity is a natural or constructed landform or surface characteristic associated with a given location or area.
-
C.
involvesTerrain
Indicates that the relationship or action takes place in, across, or is directly affected by a specified type of terrain or landform.
-
D.
terrainCapability
Indicates the types of terrain or ground conditions in which an entity can effectively operate or function.
-
E.
hasTerrainFor
Indicates that a location or area possesses terrain suitable or designated for a particular use, activity, or feature.
- F. None of above. chosen
Provenance (4 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_69d889d7d27c819088486ce3f0627fa1 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43b08d5a881909e7a5b2ae2c60898 |
completed | April 19, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69e3b02e6cc88190986e85e64ce9383e |
completed | April 18, 2026, 4:24 p.m. |
| PDg | Predicate description generation | batch_69e3b2a33e8481908fa6ef45290d08aa |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:46 a.m.