Triple
T34390164
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gaius Pius Esuvius Tetricus |
E882672
|
entity |
| Predicate | hasReignType |
P198835
|
FINISHED |
| Object | breakaway rule |
—
|
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: breakaway rule | Statement: [Gaius Pius Esuvius Tetricus, hasReignType, breakaway rule]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReignType Context triple: [Gaius Pius Esuvius Tetricus, hasReignType, breakaway rule]
-
A.
hasTypeOfRulership
chosen
Indicates that one entity exercises a specific kind or form of rulership or governing authority over another.
-
B.
reignIs
Indicates that one entity holds ruling authority or sovereignty over another for a specified period.
-
C.
reignTo
Indicates that one entity exercises ruling authority or governance over another entity or domain during a particular period.
-
D.
typeOfReignMarker
Indicates that something serves as a marker or indicator denoting the type or nature of a particular reign or period of rule.
-
E.
reignStatus
Indicates the status or condition of an entity’s period of rule or governance, such as whether it is ongoing, completed, or otherwise characterized.
- 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_69f349c0219881909393bbbc1edc8161 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.