Triple
T8563374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaceport America |
E202741
|
entity |
| Predicate | firstPoweredSpaceflightFrom |
P83660
|
FINISHED |
| Object | 2018 |
—
|
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: 2018 | Statement: [Spaceport America, firstPoweredSpaceflightFrom, 2018]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPoweredSpaceflightFrom Context triple: [Spaceport America, firstPoweredSpaceflightFrom, 2018]
-
A.
firstSpaceflight
Indicates that the subject entity performed, experienced, or was responsible for its earliest occurrence of traveling into outer space.
-
B.
firstCrewedMission
Indicates that the mission is the first instance in which humans were onboard or directly participated as crew.
-
C.
firstSuccessfulOrbitalLaunch
Indicates that the event is the earliest instance in which a launch successfully placed a payload into a stable orbit around a celestial body.
-
D.
isFirstSpacecraftTo
Indicates that a spacecraft is the earliest or initial one to reach, visit, or achieve a specified destination or milestone.
-
E.
firstHumanInSpace
Indicates that the subject is the first human ever to travel into outer space.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe9cfc4a48190ae4530d3614d115f |
completed | March 31, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69cbd1160fcc8190aa380a73610af731 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30e37ac8190b685df36274602b5 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:20 p.m.