Triple
T10497129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pannonia Inferior |
E247565
|
entity |
| Predicate | romanProvinceType |
P94476
|
FINISHED |
| Object | imperial 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: imperial province | Statement: [Pannonia Inferior, romanProvinceType, imperial province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: romanProvinceType Context triple: [Pannonia Inferior, romanProvinceType, imperial province]
-
A.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
B.
romanProvinceRelation
Indicates a relationship where one entity functioned as, or was part of, a Roman province administered by another entity.
-
C.
romanProvinceFormation
Indicates the establishment or formal organization of a territory as a Roman province under Roman administrative control.
-
D.
RomanProvinceContext
Indicates that the subject entity is situated within, associated with, or understood in the administrative and cultural framework of a Roman province.
-
E.
romanProvinceOpposite
Indicates that two Roman provinces are located on opposite sides of a defined geographic feature or boundary, such as a sea, river, or frontier line.
- 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_69d381c309b88190af78aa681cf6a4c2 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d5098d8ac481909c4adedbc4ad1c03 |
completed | April 7, 2026, 1:41 p.m. |
| PD | Predicate disambiguation | batch_69d4fb8e24ac8190912c9f11b8bd3084 |
completed | April 7, 2026, 12:41 p.m. |
| PDg | Predicate description generation | batch_69d4fe46a6448190b061bc3545835cad |
completed | April 7, 2026, 12:53 p.m. |
Created at: April 6, 2026, 12:24 p.m.