Triple
T34985264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 6–9 bus |
E1008925
|
entity |
| Predicate | firstUseLaunchDate |
—
|
GENERATED |
| Object | 1965-12-16 |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstUseLaunchDate Context triple: [Pioneer 6–9 bus, firstUseLaunchDate, 1965-12-16]
-
A.
firstSuccessfulLaunchDate
Indicates the calendar date on which an entity achieved its first successful launch.
-
B.
firstUsedOn
chosen
Indicates the date, time, or context in which something was initially applied, activated, or put into use on a particular object or entity.
-
C.
firstUsedAt
Indicates the time or place at which something was initially used or put into operation.
-
D.
firstUsedAs
Indicates that one entity was the earliest or original thing in which another entity was used or applied.
-
E.
firstBetaReleaseDate
Indicates the calendar date on which the first beta version of something was released.
- F. None of above.
Provenance (1 batch)
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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:01 p.m.