Triple
T32282481
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tracy’s Rock |
E824737
|
entity |
| Predicate | missionLandingSiteRegion |
P37290
|
FINISHED |
| Object | Taurus–Littrow valley landing site |
—
|
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: Taurus–Littrow valley landing site | Statement: [Tracy’s Rock, missionLandingSiteRegion, Taurus–Littrow valley landing site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionLandingSiteRegion Context triple: [Tracy’s Rock, missionLandingSiteRegion, Taurus–Littrow valley landing site]
-
A.
targetRegionOnMars
Indicates that an entity designates or is associated with a specific geographic region located on the planet Mars.
-
B.
planetRegion
Indicates that a specified region or area is located on or associated with a particular planet.
-
C.
firstLandingSite
Indicates the location where an entity initially arrives, lands, or touches down before any subsequent movements or landings.
-
D.
lunarLandingRegion
chosen
Indicates the geographic region on the Moon where a spacecraft or mission has landed.
-
E.
wasLandingSiteOf
Indicates that a location served as the site where a landing event (such as a spacecraft, aircraft, or vehicle) took place.
- 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c8159edc8190b1c87015e0c820e8 |
completed | May 3, 2026, 3:59 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
Created at: May 1, 2026, 12:43 a.m.