Triple
T31489097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bird in Space |
E803358
|
entity |
| Predicate | notableVersionDate |
P190080
|
FINISHED |
| Object | 1923–1924 |
—
|
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: 1923–1924 | Statement: [Bird in Space, notableVersionDate, 1923–1924]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableVersionDate Context triple: [Bird in Space, notableVersionDate, 1923–1924]
-
A.
notableVersionType
Indicates that one version of an entity is recognized as particularly significant or noteworthy relative to other versions.
-
B.
notableOperationDate
Indicates the date on which a significant or noteworthy operation, event, or activity associated with an entity took place.
-
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.
releaseYearOfNotableVersion
chosen
Indicates the calendar year in which a notable or significant version of something was released.
-
E.
notableCaseDate
Indicates the date on which a particular case or legal matter became notable or was formally recognized as significant.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:37 p.m.