Triple
T7523747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Shuttle Challenger |
E177839
|
entity |
| Predicate | rolloutDate |
P77313
|
FINISHED |
| Object | 1982-06-30 |
—
|
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: 1982-06-30 | Statement: [Space Shuttle Challenger, rolloutDate, 1982-06-30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rolloutDate Context triple: [Space Shuttle Challenger, rolloutDate, 1982-06-30]
-
A.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
-
B.
releasedAt
Indicates the time or date at which something (such as a product, work, or item) is made publicly available or officially launched.
-
C.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
D.
originallyScheduledReleaseDate
Indicates the date on which something was first planned or intended to be released, before any later changes or rescheduling.
-
E.
launchDateNote
Indicates a note or qualifier providing additional information or context about an entity’s launch date.
- 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_69c69f29bf3081909a146aec7755f185 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f7c4f32081908b5162f4551adb6d |
completed | March 27, 2026, 9:33 p.m. |
| PD | Predicate disambiguation | batch_69c6f4d6bb808190bdd04499fd3bceb6 |
completed | March 27, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69c6f555455c81908850210bcad96ac2 |
completed | March 27, 2026, 9:23 p.m. |
Created at: March 27, 2026, 3:46 p.m.