Triple
T33731832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 16 landing site |
E864293
|
entity |
| Predicate | missionLunarLiftoffDateUTC |
P38962
|
FINISHED |
| Object | 1972-04-24T01:25:47Z |
—
|
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: 1972-04-24T01:25:47Z | Statement: [Apollo 16 landing site, missionLunarLiftoffDateUTC, 1972-04-24T01:25:47Z]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionLunarLiftoffDateUTC Context triple: [Apollo 16 landing site, missionLunarLiftoffDateUTC, 1972-04-24T01:25:47Z]
-
A.
lunarLiftoffDate
chosen
Indicates the date on which a spacecraft or mission lifts off from the lunar surface.
-
B.
lunarLandingTimeUTC
Indicates the exact time, in Coordinated Universal Time (UTC), at which a lunar landing event occurs.
-
C.
yearOfFirstCrewedLunarLanding
Indicates the calendar year in which the first crewed lunar landing took place.
-
D.
lunarMission
Indicates a mission or operation specifically directed toward exploring, studying, or traveling to the Moon.
-
E.
yearOfLunarLanding
Indicates the specific calendar year in which a particular lunar landing event took place.
- 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_69f3498a64cc8190b4b414c67b280d93 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f757898fe48190b124dc7301672623 |
completed | May 3, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69f754c484348190948d2a04ff228fb1 |
completed | May 3, 2026, 1:59 p.m. |
Created at: May 1, 2026, 1:44 a.m.