Triple
T11205825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Turin Royal Canon |
E265158
|
entity |
| Predicate | estimatedCenturyBCE |
P11259
|
FINISHED |
| Object | 13th century BCE |
—
|
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: 13th century BCE | Statement: [Turin Royal Canon, estimatedCenturyBCE, 13th century BCE]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: estimatedCenturyBCE Context triple: [Turin Royal Canon, estimatedCenturyBCE, 13th century BCE]
-
A.
approximateBirthCenturyBCE
Indicates that an entity’s birth is estimated to have occurred within a specified century before the Common Era (BCE), rather than on an exact year or date.
-
B.
approximateStartCenturyBC
chosen
Indicates that an entity’s starting time or occurrence is approximately located within a specified century before the Common Era (BC).
-
C.
approximateUseEndCenturyBC
Indicates an estimated century BCE by which the use or activity associated with the subject is believed to have ended.
-
D.
dateToCenturyBCE
Indicates the mapping of a specific calendar date to the century before the Common Era (BCE) in which that date falls.
-
E.
baseAfter1stCentury
Indicates that something is based in a time period occurring after the 1st century.
- 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_69d6aa9eb9248190b20211772621b4bc |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8d4eef88190a7f05bca82d919b9 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf83464819087529d47d025d313 |
completed | April 9, 2026, 8:02 a.m. |
Created at: April 8, 2026, 9:30 p.m.