Triple
T9449073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauretania Caesariensis |
E227838
|
entity |
| Predicate | roleInRomanSystem |
P88236
|
FINISHED |
| Object | frontier province |
—
|
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: frontier province | Statement: [Mauretania Caesariensis, roleInRomanSystem, frontier province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInRomanSystem Context triple: [Mauretania Caesariensis, roleInRomanSystem, frontier province]
-
A.
RomanNumeral
Indicates that something is represented or written using the Roman numeral system.
-
B.
usesRomanNumerals
Indicates that something represents numbers or sequences using the Roman numeral system rather than standard Arabic digits.
-
C.
hasRomanEquivalent
Indicates that one entity corresponds to or is equivalent to another entity within the context of Roman culture, naming, or classification.
-
D.
fullRomanName
Indicates that one entity is the complete Roman-style personal name (including all components) corresponding to another entity.
-
E.
preRomanName
Indicates the name by which an entity (such as a place or people) was known before the Roman period or prior to receiving a Roman-era name.
- F. None of above. chosen
Provenance (4 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_69ca8439f8bc8190997f2ef40c9f0bc2 |
completed | March 30, 2026, 2:10 p.m. |
| NER | Named-entity recognition | batch_69cd7f64fdc88190aec27793bfe62d77 |
completed | April 1, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69cca5596ffc819097e9c8eefd4ef9b8 |
completed | April 1, 2026, 4:55 a.m. |
| PDg | Predicate description generation | batch_69cca89d0f0c8190b4528990fe708fca |
completed | April 1, 2026, 5:09 a.m. |
Created at: March 30, 2026, 7:51 p.m.