Triple
T33731840
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 landing site |
E864293
|
entity |
| Predicate | missionSequenceLunarLanding |
P181096
|
FINISHED |
| Object | 5th crewed lunar landing |
—
|
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: 5th crewed lunar landing | Statement: [Apollo 16 landing site, missionSequenceLunarLanding, 5th crewed lunar landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSequenceLunarLanding Context triple: [Apollo 16 landing site, missionSequenceLunarLanding, 5th crewed lunar landing]
-
A.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
B.
plannedFirstLunarLanding
Indicates that an entity is responsible for organizing or scheduling the earliest intended mission to land on the Moon.
-
C.
lunarMissionCommanded
Indicates that an entity served as the commanding leader of a specified lunar mission.
-
D.
firstMannedLunarLandingMission
Indicates that the subject is the first crewed space mission to successfully land humans on the Moon.
-
E.
plannedFirstCrewedLunarLandingMission
Indicates that an entity is designated as the mission planned to perform the first crewed landing on the Moon.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
| PDg | Predicate description generation | batch_69f760a2a90c8190b8fbc55412ab752b |
completed | May 3, 2026, 2:50 p.m. |
Created at: May 1, 2026, 1:44 a.m.