Triple
T20112176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Circle of Upper Saxony |
E490359
|
entity |
| Predicate | hadFiscalRole |
P50971
|
FINISHED |
| Object | collecting and apportioning imperial taxes |
—
|
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: collecting and apportioning imperial taxes | Statement: [Circle of Upper Saxony, hadFiscalRole, collecting and apportioning imperial taxes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadFiscalRole Context triple: [Circle of Upper Saxony, hadFiscalRole, collecting and apportioning imperial taxes]
-
A.
haveFiscalPowers
chosen
Indicates that an entity possesses legal authority or control over financial or budgetary matters.
-
B.
hasEconomicRole
Indicates that an entity participates in or fulfills a specific function, position, or responsibility within an economic system or activity.
-
C.
hasCapitalRole
Indicates that an entity holds an official role, function, or status specifically associated with a capital city.
-
D.
hasSettlementRole
Indicates that an entity holds or is assigned a specific functional role or status within a settlement.
-
E.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
- 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_69da62636cc08190982cc71733a17b8d |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e666e162108190b19c9559218c8fd6 |
completed | April 20, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69e54cf788188190a46cc49c9ce7617f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:29 p.m.