Triple
T30258638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moesia Superior |
E769422
|
entity |
| Predicate | rankOfGovernor |
P1893
|
FINISHED |
| Object | legatus Augusti pro praetore |
—
|
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: legatus Augusti pro praetore | Statement: [Moesia Superior, rankOfGovernor, legatus Augusti pro praetore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rankOfGovernor Context triple: [Moesia Superior, rankOfGovernor, legatus Augusti pro praetore]
-
A.
provinceGovernor
Indicates that one entity serves as the governor or chief administrative authority of a particular province in relation to the other entity.
-
B.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
-
C.
stateOfGovernorship
Indicates the relationship in which an individual holds or held the official position and authority of governor over a specific jurisdiction.
-
D.
governorTitle
chosen
Indicates the official title or designation held by a person serving as a governor.
-
E.
governorshipType
Indicates the specific form or category of governorship associated with an office, position, or governing role.
- 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_69f22484a5f48190b678cd607700bc82 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680a734788190ae3e75d06552d571 |
completed | May 2, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:41 p.m.