Triple
T16258140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank De Winne |
E394682
|
entity |
| Predicate | firstSpaceflightYear |
P32565
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Frank De Winne, firstSpaceflightYear, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSpaceflightYear Context triple: [Frank De Winne, firstSpaceflightYear, 2002]
-
A.
firstSpaceflight
chosen
Indicates that the subject entity performed, experienced, or was responsible for its earliest occurrence of traveling into outer space.
-
B.
firstSpaceflightOf
Indicates that the object is the first spaceflight mission associated with the subject (such as a person, vehicle, or program).
-
C.
firstCrewedLaunchFrom
Indicates the location from which an entity conducted its first crewed (human-carrying) launch.
-
D.
firstCrewedTestFlightYear
Indicates the calendar year in which an entity conducted its first test flight involving a human crew.
-
E.
firstSuccessfulCrewedMissionDate
Indicates the calendar date on which the first crewed mission associated with the subject was successfully completed.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245c1fa208190995feaeba766b45f |
completed | April 17, 2026, 2:37 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:04 a.m.