Triple
T28660817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diocese of Hispania |
E725461
|
entity |
| Predicate | hasTypeOfGovernor |
P90690
|
FINISHED |
| Object | vicarius |
—
|
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: vicarius | Statement: [Diocese of Hispania, hasTypeOfGovernor, vicarius]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypeOfGovernor Context triple: [Diocese of Hispania, hasTypeOfGovernor, vicarius]
-
A.
governorateType
Indicates the specific classification or category of a governorate within an administrative or governmental hierarchy.
-
B.
governorshipType
chosen
Indicates the specific form or category of governorship associated with an office, position, or governing role.
-
C.
hasRankOfGovernor
Indicates that an entity holds the official position or rank of governor in relation to a specified jurisdiction or organization.
-
D.
hasGovernorPer
Indicates that a person serves as the governor of a particular political or administrative entity.
-
E.
hasResidentGovernor
Indicates that a place or territory has an officially appointed governor who resides there and exercises governing authority over it.
- 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_69f01d84f5f0819087ab5e6143b14ed7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
Created at: April 28, 2026, 4:58 a.m.