Triple
T27985291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contestania |
E706726
|
entity |
| Predicate | laterRomanAdministration |
P52600
|
FINISHED |
| Object | Carthaginensis |
—
|
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: Carthaginensis | Statement: [Contestania, laterRomanAdministration, Carthaginensis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRomanAdministration Context triple: [Contestania, laterRomanAdministration, Carthaginensis]
-
A.
laterRomanAdministrativeUnit
chosen
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
-
B.
imperialAdministration
Indicates the exercise or structure of centralized governing authority by an empire over its territories or subjects.
-
C.
romanGovernmentForm
Indicates the form or type of government used in the context of ancient Rome.
-
D.
statusInLateEmpire
Indicates the social, legal, or political standing an entity held during the later period of an empire.
-
E.
statusAfterRomanConquest
Indicates the condition or standing of an entity following its conquest by the Roman state or Roman forces.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: April 27, 2026, 7:47 p.m.