Triple
T25224267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Klingon language |
E632049
|
entity |
| Predicate | hasYearOfFirstPublication |
P62840
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Klingon language, hasYearOfFirstPublication, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasYearOfFirstPublication Context triple: [Klingon language, hasYearOfFirstPublication, 1985]
-
A.
firstPublishedInWorkYear
Indicates the year in which a work was first published.
-
B.
firstAssociatedPublicationYear
chosen
Indicates the calendar year in which an entity’s earliest associated publication was first released or made publicly available.
-
C.
firstCompletePublicationYear
Indicates the calendar year in which an entity’s first complete publication was released.
-
D.
firstStandardPublicationYear
Indicates the year in which an entity’s work was first formally published according to a recognized standard or official publication record.
-
E.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
- 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_69e75a8e0f688190a7aebe9a4815e25b |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47cc23da88190bad7b9a28e09898b |
completed | May 1, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f44d849e7c81909945438f40e35362 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 21, 2026, 1:03 p.m.