Triple
T28410764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | legatus Augusti pro praetore |
E719655
|
entity |
| Predicate | governedTypeOfProvince |
P21121
|
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: [legatus Augusti pro praetore, governedTypeOfProvince, imperial province]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governedTypeOfProvince Context triple: [legatus Augusti pro praetore, governedTypeOfProvince, imperial province]
-
A.
governedType
Indicates that one entity determines, constrains, or regulates the type or classification of another entity.
-
B.
governedCityStateType
Indicates that a city is governed under a particular type or form of state-level governance.
-
C.
governingProvince
Indicates that one administrative unit or authority has official governing control over a specified province.
-
D.
governsTerritoryType
chosen
Indicates that an authority or governing body exercises official control or administration over a specified type of territory.
-
E.
governedIn
Indicates that one entity exercised governing authority or administrative control within a specified place or jurisdiction.
- 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fe6b7c785c8190aaab06019f571434 |
completed | May 8, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fe68edef20819081c77f9607b944dd |
completed | May 8, 2026, 10:51 p.m. |
Created at: April 28, 2026, 1:26 a.m.