Triple
T22201518
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LC-5 |
E548695
|
entity |
| Predicate | firstCrewedLaunch |
P146819
|
FINISHED |
| Object | 1961-05-05 |
—
|
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: 1961-05-05 | Statement: [LC-5, firstCrewedLaunch, 1961-05-05]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstCrewedLaunch Context triple: [LC-5, firstCrewedLaunch, 1961-05-05]
-
A.
firstCrewedLaunchFrom
Indicates the location from which an entity conducted its first crewed (human-carrying) launch.
-
B.
firstCrewedLaunchVehicle
Indicates that the subject is the first launch vehicle to carry a crewed (human-occupied) spacecraft for the associated space program, organization, or context.
-
C.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
-
D.
firstSuccessfulCrewedMissionDate
Indicates the calendar date on which the first crewed mission associated with the subject was successfully completed.
-
E.
firstSuccessfulCrewedMission
Indicates that the subject entity is the earliest crewed mission to achieve a specified success criterion for the object entity (such as a destination, program, or objective).
- 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_69e11e3ecc7c8190b5f94cd8f42e9d37 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12aeb16348190a34f96b47e01c8cf |
completed | April 28, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e71b48576c8190a8e93738fd9cfda5 |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:36 p.m.