Triple
T13606350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lycaonians |
E325072
|
entity |
| Predicate | regionStatusInEmpire |
P23251
|
FINISHED |
| Object | Roman province of Galatia (partly) |
—
|
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: Roman province of Galatia (partly) | Statement: [Lycaonians, regionStatusInEmpire, Roman province of Galatia (partly)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionStatusInEmpire Context triple: [Lycaonians, regionStatusInEmpire, Roman province of Galatia (partly)]
-
A.
legalStatusInEmpire
Indicates the formal legal standing or classification an entity holds within a particular empire’s legal and administrative system.
-
B.
regionStatus
chosen
Indicates the current condition, classification, or operational state assigned to a specific geographic or administrative region.
-
C.
positionOnEmpire
Indicates that one entity holds a specific role, rank, or status within the hierarchical structure of an empire in relation to another entity.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
regionOfDynasty
Indicates the geographic region or area in which a given dynasty held power or was primarily based.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae1b3ee481909bd43ded6227a3e5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:50 p.m.