Triple
T31494205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mount Sharp |
E803489
|
entity |
| Predicate | nearLandingSite |
P20108
|
FINISHED |
| Object | Bradbury Landing |
—
|
NE NERFINISHED |
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: Bradbury Landing | Statement: [Mount Sharp, nearLandingSite, Bradbury Landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearLandingSite Context triple: [Mount Sharp, nearLandingSite, Bradbury Landing]
-
A.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
B.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
C.
landedNear
chosen
Indicates that one entity has come to rest on a surface or location in close proximity to another specified entity or reference point.
-
D.
initialLandingSite
Indicates the location where an entity first arrives, lands, or makes its initial touchdown.
-
E.
approachAndLandingTestsLocation
Indicates the location where approach and landing tests are conducted.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a1e76f98819084babaa80607b5ed |
completed | May 3, 2026, 1:16 a.m. |
| PD | Predicate disambiguation | batch_69f69fe82e5c81909da9db0a2f3bba6d |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 9:40 p.m.