Triple
T32682120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Camelot crater |
E835613
|
entity |
| Predicate | missionLandingSiteProximity |
P53174
|
FINISHED |
| Object | Apollo 17 LM Challenger 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: Apollo 17 LM Challenger landing site | Statement: [Camelot crater, missionLandingSiteProximity, Apollo 17 LM Challenger landing site]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionLandingSiteProximity Context triple: [Camelot crater, missionLandingSiteProximity, Apollo 17 LM Challenger landing site]
-
A.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
B.
distanceToAstros
Indicates the measured or calculated distance between an entity and the Astros.
-
C.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
D.
proximityToLandmark
chosen
Indicates a spatial relationship where one entity is located near or close to a specified landmark.
-
E.
hasLandedProbeTarget
Indicates that a space probe has successfully landed on the specified target body or location.
- 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_69f3493211388190993801216afbc2a7 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:09 a.m.