Triple
T30540144
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reign of Caracalla |
E777250
|
entity |
| Predicate | coRulerAtStart |
P13111
|
FINISHED |
| Object | Geta |
—
|
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: Geta | Statement: [Reign of Caracalla, coRulerAtStart, Geta]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coRulerAtStart Context triple: [Reign of Caracalla, coRulerAtStart, Geta]
-
A.
coRulerWith
chosen
Indicates that two or more entities share ruling authority over the same domain or polity at the same time.
-
B.
coRulerAfterDeath
Indicates that one entity became a co-ruler with another entity only after the latter had died.
-
C.
rulerDuringConstruction
Indicates that a particular person held ruling authority over a place or polity during the time a specific construction project was carried out.
-
D.
currentRuler
Indicates that one entity is the present reigning ruler or head of state of another entity (such as a country, region, or polity).
-
E.
involvesRuler
Indicates that the relationship or action includes or pertains to a ruler as a participating party.
- 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_69f2249d183c8190b79937c1768d2163 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6888953688190ae6709934cc9fccd |
completed | May 2, 2026, 11:28 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 29, 2026, 8:19 p.m.