Triple
T4425904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Falcon 1 launch pad, Omelek Island |
E95207
|
entity |
| Predicate | notableLaunchDate |
P7203
|
FINISHED |
| Object | 2008-09-28 |
—
|
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: 2008-09-28 | Statement: [Falcon 1 launch pad, Omelek Island, notableLaunchDate, 2008-09-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableLaunchDate Context triple: [Falcon 1 launch pad, Omelek Island, notableLaunchDate, 2008-09-28]
-
A.
launchDateNote
Indicates a note or qualifier providing additional information or context about an entity’s launch date.
-
B.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
C.
notableRelease
Indicates that an entity is a significant or prominent release (such as a major version, edition, or launch) associated with another entity.
-
D.
launchedAt
Indicates the specific time or event at which something (such as a product, project, or mission) was initiated or set into operation.
-
E.
firstSuccessfulLaunchDate
chosen
Indicates the calendar date on which an entity achieved its first successful launch.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554e40ec8190982acc0948da2f42 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:30 p.m.