Triple
T19074904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Codex Leningradensis |
E466878
|
entity |
| Predicate | colophonStates |
P134224
|
FINISHED |
| Object | copied in 1008 CE |
—
|
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: copied in 1008 CE | Statement: [Codex Leningradensis, colophonStates, copied in 1008 CE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: colophonStates Context triple: [Codex Leningradensis, colophonStates, copied in 1008 CE]
-
A.
signageStates
Indicates that one entity specifies, displays, or communicates the status or condition of another entity through signage.
-
B.
stateOfPublication
Indicates the jurisdiction or territorial state in which a work is formally published or made publicly available.
-
C.
compactStates
Indicates that the states in question are geographically small and relatively uniform in shape, lacking extensive protrusions or irregular boundaries.
-
D.
primaryStates
Indicates that certain states or conditions are the main or most fundamental ones within a given context or system.
-
E.
portraysState
Indicates that one entity visually or symbolically represents or depicts the condition, status, or situation of another entity.
- F. None of above. chosen
Provenance (4 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e2e3c7b08190bf6448ead11ba916 |
completed | April 20, 2026, 8:25 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4bfe8a06081909fd5c28a33e9f218 |
completed | April 19, 2026, 11:43 a.m. |
Created at: April 10, 2026, 12:04 p.m.