Triple
T3117051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cassius Dio |
E65087
|
entity |
| Predicate | wroteAboutPeriod |
P14097
|
FINISHED |
| Object | from the founding of Rome to AD 229 |
—
|
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: from the founding of Rome to AD 229 | Statement: [Cassius Dio, wroteAboutPeriod, from the founding of Rome to AD 229]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wroteAboutPeriod Context triple: [Cassius Dio, wroteAboutPeriod, from the founding of Rome to AD 229]
-
A.
hasWrittenAbout
chosen
Indicates that one entity has authored content or material discussing, analyzing, or referencing another entity.
-
B.
refersToPeriod
Indicates that one entity designates, references, or is associated with a specific time period or interval.
-
C.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
D.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
E.
notableWorkPeriod
Indicates the time span during which an entity produced or was associated with its most significant or well-known works.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada4e5d1488190a2ab199625fdf05d |
completed | March 8, 2026, 4:33 p.m. |
| PD | Predicate disambiguation | batch_69ad9df455088190940ad04419772dc8 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:04 p.m.