Triple
T10788137
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scythia Minor |
E254500
|
entity |
| Predicate | wasRomanProvince |
P95485
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Scythia Minor, wasRomanProvince, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasRomanProvince Context triple: [Scythia Minor, wasRomanProvince, yes]
-
A.
wasRomanProtectorate
Indicates that one political entity was under the protection and partial control of the Roman state as a protectorate.
-
B.
romanProvinceType
Indicates that an entity is classified as a specific type or category of Roman province.
-
C.
romanProvinceAfterConquest
Indicates that a territory became a Roman province following its military conquest by Rome.
-
D.
romanProvinceRelation
Indicates a relationship where one entity functioned as, or was part of, a Roman province administered by another entity.
-
E.
laterRomanAdministrativeUnit
Indicates that one entity functioned as an administrative unit within the later Roman Empire in relation to another entity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d65fcc8190ab5573a861409c56 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
| PDg | Predicate description generation | batch_69d6fa334b8c819082eaf8537084c323 |
completed | April 9, 2026, 1 a.m. |
Created at: April 8, 2026, 9:17 p.m.