Triple
T36064507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luna 15 |
E1043182
|
entity |
| Predicate | launchDateRelativeToApollo11 |
P186418
|
FINISHED |
| Object | launched three days before Apollo 11 launch |
—
|
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: launched three days before Apollo 11 launch | Statement: [Luna 15, launchDateRelativeToApollo11, launched three days before Apollo 11 launch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchDateRelativeToApollo11 Context triple: [Luna 15, launchDateRelativeToApollo11, launched three days before Apollo 11 launch]
-
A.
yearOfFirstCrewedLunarLanding
Indicates the calendar year in which the first crewed lunar landing took place.
-
B.
lunarLiftoffDate
Indicates the date on which a spacecraft or mission lifts off from the lunar surface.
-
C.
firstLunarLandingDate
Indicates the calendar date on which an entity’s first lunar landing occurred.
-
D.
yearOfLunarLanding
Indicates the specific calendar year in which a particular lunar landing event took place.
-
E.
launchDateOfFirstHumanSpaceflight
Indicates the calendar date on which the first human spaceflight associated with the given entity was launched.
- 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_69f76e2f09448190b0486d5ecad5e243 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7cec398ac819081c954a993c323ee |
completed | May 3, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:08 p.m.