Triple
T28824503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Britannia Superior |
E727864
|
entity |
| Predicate | hasRankOfGovernor |
P179487
|
FINISHED |
| Object | consular legate |
—
|
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: consular legate | Statement: [Britannia Superior, hasRankOfGovernor, consular legate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankOfGovernor Context triple: [Britannia Superior, hasRankOfGovernor, consular legate]
-
A.
hasResidentGovernor
Indicates that a place or territory has an officially appointed governor who resides there and exercises governing authority over it.
-
B.
succeededInOfficeAsGovernorBy
Indicates that one individual’s term as governor ended and was directly followed by another individual’s term in the same office.
-
C.
hadGovernor
Indicates that an administrative region or political entity was governed by a specific person who held the office of governor.
-
D.
governorateOf
Indicates that one entity is the governorate (administrative region) to which another entity belongs or is located within.
-
E.
hasRegionalGovernor
Indicates that a region is administered or overseen by a specific governor responsible for its governance.
- 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_69f0319d09088190bbf14cdf1987792a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f722c1bc648190a79bfdc722dcaaa4 |
completed | May 3, 2026, 10:26 a.m. |
| PD | Predicate disambiguation | batch_69f72153a9188190b02adc84e1be4af8 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: April 28, 2026, 6:35 a.m.