Triple
T34683447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Imperial City of Ulm |
E890677
|
entity |
| Predicate | hasSovereigntyLevel |
P5545
|
FINISHED |
| Object | imperial immediacy |
—
|
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 immediacy | Statement: [Free Imperial City of Ulm, hasSovereigntyLevel, imperial immediacy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSovereigntyLevel Context triple: [Free Imperial City of Ulm, hasSovereigntyLevel, imperial immediacy]
-
A.
hasSovereignAuthority
Indicates that one entity holds ultimate governing or ruling power over another entity or domain.
-
B.
hasSovereignPowerOver
Indicates that one entity holds ultimate governing authority or supreme ruling power over another entity.
-
C.
hasSovereignRights
Indicates that an entity possesses recognized supreme authority and legal control over a territory, resource, or domain.
-
D.
hasSovereignPowers
Indicates that an entity possesses ultimate governing authority or supreme political power over a territory or population.
-
E.
sovereigntyStatus
chosen
Indicates the degree and type of political independence or control an entity holds over its own territory and governance.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: May 1, 2026, 2:05 a.m.