Triple
T31322783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Force |
E798793
|
entity |
| Predicate | firstSeasonReleaseDate |
P2596
|
FINISHED |
| Object | 2020-05-29 |
—
|
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: 2020-05-29 | Statement: [Space Force, firstSeasonReleaseDate, 2020-05-29]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonReleaseDate Context triple: [Space Force, firstSeasonReleaseDate, 2020-05-29]
-
A.
firstSeasonReleaseYear
Indicates the calendar year in which the first season of something (such as a series or competition) was initially released or premiered.
-
B.
firstAired
chosen
Indicates the date on which something (such as a show, episode, or broadcast content) was first aired or publicly transmitted.
-
C.
firstSeasonEndYear
Indicates the calendar year in which an entity’s first season or initial seasonal run concluded.
-
D.
firstSeasonScheduled
Indicates that the initial season of an entity (such as a show, competition, or event series) has been planned and assigned a schedule.
-
E.
firstSeasonOf
Indicates that one entity is the first season installment belonging to the series or show represented by the other entity.
- 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_69f224e3238c8190b2291f50ea4962cd |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:15 p.m.