Triple
T34643536
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surveyor 3 landing site |
E889633
|
entity |
| Predicate | precisionLandingDemonstration |
P179560
|
FINISHED |
| Object | Apollo 12 landing near Surveyor 3 |
—
|
LITERAL FINISHED |
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 12 landing near Surveyor 3 | Statement: [Surveyor 3 landing site, precisionLandingDemonstration, Apollo 12 landing near Surveyor 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precisionLandingDemonstration Context triple: [Surveyor 3 landing site, precisionLandingDemonstration, Apollo 12 landing near Surveyor 3]
-
A.
plannedLandingMethod
Indicates that an entity has designated a specific method or procedure to be used for its landing.
-
B.
approachAndLandingTestsLocation
Indicates the location where approach and landing tests are conducted.
-
C.
runwayLanding
Indicates that an aircraft performs a landing operation on a specific runway.
-
D.
lunarLander
Indicates a relationship in which an entity functions as or is used as a lunar lander, designed to land on the surface of the Moon.
-
E.
landingRecovery
Indicates the process or method by which something is retrieved or secured after it has landed.
- 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_69f349d825c88190bfc6170ac9281260 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.