Triple
T33839525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 15 landing site |
E867321
|
entity |
| Predicate | landingOfMission |
P82004
|
FINISHED |
| Object | Apollo 15 |
—
|
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 15 | Statement: [Apollo 15 landing site, landingOfMission, Apollo 15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: landingOfMission Context triple: [Apollo 15 landing site, landingOfMission, Apollo 15]
-
A.
dateOfLanding
Indicates the specific calendar date on which a landing event took place.
-
B.
planetaryBodyLandedOn
Indicates that one entity has successfully landed on the surface of a planetary body (such as a planet, moon, or asteroid).
-
C.
plannedLandingSiteType
Indicates the type or category of location designated as the intended landing site.
-
D.
firstLandingSite
Indicates the location where an entity initially arrives, lands, or touches down before any subsequent movements or landings.
-
E.
wasLandingSiteIn
chosen
Indicates that a specific landing event occurred at or within the location denoted by the related entity.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:47 a.m.