Triple
T33212269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interior Exploration using Seismic Investigations, Geodesy and Heat Transport |
E850191
|
entity |
| Predicate | planetaryBodyLandedOn |
P176200
|
FINISHED |
| Object | Mars |
—
|
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: Mars | Statement: [Interior Exploration using Seismic Investigations, Geodesy and Heat Transport, planetaryBodyLandedOn, Mars]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: planetaryBodyLandedOn Context triple: [Interior Exploration using Seismic Investigations, Geodesy and Heat Transport, planetaryBodyLandedOn, Mars]
-
A.
hasLandingSystem
Indicates that an entity is equipped with or utilizes a particular landing system for performing landings.
-
B.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
C.
wasLandingSiteOf
Indicates that a location served as the site where a landing event (such as a spacecraft, aircraft, or vehicle) took place.
-
D.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
E.
wasLandingSiteForAstronaut
Indicates that a particular location served as the landing site for an astronaut.
- 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_69f3495fb92c819083ce65d0ddee7a76 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6dd3cc0648190a275812d6711275a |
completed | May 3, 2026, 5:29 a.m. |
| PD | Predicate disambiguation | batch_69f6d82eaee081908f06a71546315aea |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6dd3b335481909e24d4eb5b0269f9 |
completed | May 3, 2026, 5:29 a.m. |
Created at: May 1, 2026, 1:30 a.m.