Triple
T10166525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Turin (312) |
E235217
|
entity |
| Predicate | dateInCentury |
P92189
|
FINISHED |
| Object | 4th 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: 4th century | Statement: [Battle of Turin (312), dateInCentury, 4th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateInCentury Context triple: [Battle of Turin (312), dateInCentury, 4th century]
-
A.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
-
B.
dateToCenturyBCE
Indicates the mapping of a specific calendar date to the century before the Common Era (BCE) in which that date falls.
-
C.
currentStructureDatesToCentury
Indicates that the existing structure was originally built or last fundamentally constructed in the specified century.
-
D.
convertedInCentury
Indicates that an entity underwent a conversion (e.g., religious, functional, or status change) during a specified century.
-
E.
standardizedInCentury
Indicates that something was standardized or formally established according to a common norm during a specified century.
- 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_69ca84ceafd0819085828600e11bed6b |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdec6e016c81909ded2a16b839c405 |
completed | April 2, 2026, 4:11 a.m. |
| PD | Predicate disambiguation | batch_69cd4ba9956c8190a3e15d091e33149d |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd4fed19d481909d2c7ff1114664b6 |
completed | April 1, 2026, 5:03 p.m. |
Created at: March 30, 2026, 9:10 p.m.