Triple
T31490686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ulpia Severina |
E803395
|
entity |
| Predicate | possibleReignLocation |
P53632
|
FINISHED |
| Object | Rome |
—
|
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: Rome | Statement: [Ulpia Severina, possibleReignLocation, Rome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: possibleReignLocation Context triple: [Ulpia Severina, possibleReignLocation, Rome]
-
A.
reignLocation
chosen
Indicates the place or territory over which an entity rules or exercises sovereign authority.
-
B.
possibleLocation
Indicates that an entity may be located at, or could plausibly occur in, a specified place or spatial context.
-
C.
possibleReignPeriod
Indicates a time interval during which an entity could have held ruling authority, without asserting that it definitively did so.
-
D.
historicalLocationOf
Indicates that a place served as a significant site or setting for an entity during a particular historical period or event.
-
E.
possiblePlaceOfMission
Indicates that a location is a plausible or candidate site where a mission may have taken place or could take place.
- 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_69f348ca04508190ba9379b5329dfd75 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: April 30, 2026, 9:38 p.m.