Triple
T33600981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Historiae Romanae |
E860719
|
entity |
| Predicate | coversReign |
P9743
|
FINISHED |
| Object | Augustus |
—
|
NE NERFINISHED |
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: Augustus | Statement: [Historiae Romanae, coversReign, Augustus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversReign Context triple: [Historiae Romanae, coversReign, Augustus]
-
A.
reignCoverage
Indicates the temporal span or extent over which a ruler’s reign or authority is in effect.
-
B.
coversFrom
Indicates that one entity provides protection, concealment, or shelter for another entity against something originating from a specified source or direction.
-
C.
describesReignOf
chosen
Indicates that something (such as a text, record, or account) provides information about the period during which a particular ruler or authority was in power.
-
D.
correspondsToReignOf
Indicates that something (such as a time period, event, or record) matches or is associated with the duration of a specific ruler’s reign.
-
E.
coversTo
Indicates that one entity extends its coverage or protective scope to include 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_69f3497f35908190a2e9bbb9b96c7a3f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: May 1, 2026, 1:41 a.m.