Triple
T5475415
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Atlanticus |
E122939
|
entity |
| Predicate | compilationDate |
P6964
|
FINISHED |
| Object | late 16th century |
—
|
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: late 16th century | Statement: [Codex Atlanticus, compilationDate, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: compilationDate Context triple: [Codex Atlanticus, compilationDate, late 16th century]
-
A.
dateOfComposition
chosen
Indicates the calendar date or time period when a particular work was created or composed.
-
B.
compilationStatus
Indicates the current state or outcome of a compilation process for a given entity (e.g., whether it is pending, in progress, successful, or failed).
-
C.
compiledIn
Indicates that a piece of code, program, or module was compiled within or for a specific environment, system, or context.
-
D.
cataloguedDate
Indicates the date on which an item or entity was formally recorded or entered into a catalog or database.
-
E.
commissionedAt
Indicates the time or date at which something (such as a work, project, or task) was formally commissioned or initiated.
- 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_69bd46459ff48190823377457bcf7128 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd923465c88190ad9c1b75b268f7ca |
completed | March 20, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69bd91a58c448190904964a439045e05 |
completed | March 20, 2026, 6:27 p.m. |
Created at: March 20, 2026, 2:09 p.m.