Triple
T15556692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 19 |
E370887
|
entity |
| Predicate | plannedMissionProfile |
P5434
|
FINISHED |
| Object | 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: lunar landing | Statement: [Apollo 19, plannedMissionProfile, lunar landing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: plannedMissionProfile Context triple: [Apollo 19, plannedMissionProfile, lunar landing]
-
A.
missionProfile
chosen
Indicates the specific set of objectives, conditions, and operational parameters that define how a mission is planned, conducted, and evaluated.
-
B.
missionPlanning
Indicates the process of defining, organizing, and coordinating actions or operations needed to achieve a specific mission objective.
-
C.
missionPilot
Indicates that an entity serves as the pilot responsible for operating or navigating a specific mission.
-
D.
missionDurationPlanned
Indicates the length of time that a mission is scheduled or intended to last according to its plan.
-
E.
missionConfiguration
Indicates the specific setup, parameters, and conditions under which a mission is planned or executed.
- 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_69d85cc6cf40819091f4a5facee1ebe6 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04a97dbfc8190a98cbbac5e71ba88 |
completed | April 16, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69deda7e6e748190b29ccce23298afef |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:09 a.m.