Triple
T2330316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 12 |
E48386
|
entity |
| Predicate | missionSequenceInLunarLandings |
P36760
|
FINISHED |
| Object | second 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: second crewed lunar landing | Statement: [Apollo 12, missionSequenceInLunarLandings, second crewed lunar landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionSequenceInLunarLandings Context triple: [Apollo 12, missionSequenceInLunarLandings, second crewed lunar landing]
-
A.
orderOfLunarLandings
chosen
Indicates the chronological sequence in which different lunar landings occurred relative to one another.
-
B.
firstMannedLunarOrbitMission
Indicates that the subject is the first mission in which humans successfully entered into orbit around the Moon.
-
C.
lastLunarLandingMission
Indicates that the mission is the most recent one in which a spacecraft successfully landed on the Moon.
-
D.
isFifthCrewedLunarLanding
Indicates that the event is the fifth instance of a crewed lunar landing mission.
-
E.
missionHistory
Indicates the record of past missions or assignments associated with an entity, including their occurrence and relevant details.
- 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_69a88aa308a88190b0b86c011fda7fce |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:50 p.m.