Triple
T8618792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman History (Dio Cassius) |
E204108
|
entity |
| Predicate | coverageEnd |
P9332
|
FINISHED |
| Object | reign of Severan emperors |
—
|
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: reign of Severan emperors | Statement: [Roman History (Dio Cassius), coverageEnd, reign of Severan emperors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverageEnd Context triple: [Roman History (Dio Cassius), coverageEnd, reign of Severan emperors]
-
A.
coverageScope
Indicates the extent or range of entities, conditions, or situations that are included under a particular coverage or applicability.
-
B.
componentCoverage
Indicates that one entity provides coverage, protection, or support for another as one of its components or constituent parts.
-
C.
rangeEnd
chosen
Indicates the endpoint or upper boundary value of a specified range in a relationship or measurement.
-
D.
coversSection
Indicates that one entity includes, addresses, or provides content for a particular section of another entity.
-
E.
coversField
Indicates that one entity extends over, protects, or occupies the surface or area of a field associated with another entity.
- 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_69ca832ceab8819096e4a9f546695079 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc4712e74c81908b607a0ab2f9a361 |
completed | March 31, 2026, 10:13 p.m. |
| PD | Predicate disambiguation | batch_69cc455437488190b7506f820daf6e32 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:26 p.m.