Triple
T363967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo program |
E7918
|
entity |
| Predicate | firstCrewedFlightDate |
P12408
|
FINISHED |
| Object | 1968-10-11 |
—
|
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: 1968-10-11 | Statement: [Apollo program, firstCrewedFlightDate, 1968-10-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrewedFlightDate Context triple: [Apollo program, firstCrewedFlightDate, 1968-10-11]
-
A.
firstFlight
Indicates that the associated event or record corresponds to the earliest or initial flight taken or performed by the referenced entity.
-
B.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
C.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
D.
firstSuccessfulFlybyBy
Indicates that the subject is the first spacecraft or mission to successfully perform a flyby of the object specified by the predicate’s value.
-
E.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
- 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_69a2e7e880008190a6ad7e06e5d03007 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ebd1016481909b8ba3b047a47145 |
completed | Feb. 28, 2026, 1:21 p.m. |
| PD | Predicate disambiguation | batch_69a2e95c843c8190b2aba9af6e869ba1 |
completed | Feb. 28, 2026, 1:10 p.m. |
| PDg | Predicate description generation | batch_69a2ea2c44408190946267525c88e811 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.