Triple
T1358887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Justinianus |
E29052
|
entity |
| Predicate | dateOfFirstEdition |
P18405
|
FINISHED |
| Object | 529 |
—
|
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: 529 | Statement: [Codex Justinianus, dateOfFirstEdition, 529]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstEdition Context triple: [Codex Justinianus, dateOfFirstEdition, 529]
-
A.
firstEditionPublicationYear
chosen
Indicates the year in which an entity’s first edition was originally published.
-
B.
hasFirstEditionYear
Indicates the year in which the first edition of an item (such as a work, book, or publication) was originally released or published.
-
C.
firstEditionSoldOutTime
Indicates the point in time at which the first edition of an item became completely sold out.
-
D.
originallyReleasedOn
Indicates the date or platform on which something (such as a work, product, or media item) was first made publicly available.
-
E.
firstEditionType
Indicates that an entity is classified as a first edition of a work, specifying the type or category of that first edition.
- 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_69a498d77abc8190913bf57e5f51d2c4 |
completed | March 1, 2026, 7:51 p.m. |
| NER | Named-entity recognition | batch_69a4c290db288190910fcfa17e902663 |
completed | March 1, 2026, 10:49 p.m. |
| PD | Predicate disambiguation | batch_69a4bef7700c819099b294e8d9320e70 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:56 p.m.