Triple
T36572288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fra Mauro crater |
E902151
|
entity |
| Predicate | wasActualLandingSiteFor |
P174071
|
FINISHED |
| Object | Apollo 14 mission |
—
|
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 14 mission | Statement: [Fra Mauro crater, wasActualLandingSiteFor, Apollo 14 mission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasActualLandingSiteFor Context triple: [Fra Mauro crater, wasActualLandingSiteFor, Apollo 14 mission]
-
A.
wasLandingSiteOf
chosen
Indicates that a location served as the site where a landing event (such as a spacecraft, aircraft, or vehicle) took place.
-
B.
wasLandingSiteIn
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
-
C.
wasLandingSiteDuring
Indicates that a location served as the landing site for a particular event, mission, or vehicle during a specified time or context.
-
D.
firstLandingSite
Indicates the location where an entity initially arrives, lands, or touches down before any subsequent movements or landings.
-
E.
wasLandingSiteForAstronaut
Indicates that a particular location served as the landing site for an astronaut.
- 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_69f76e6416708190a9754b8c52d4e453 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:11 p.m.