Triple
T34683587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Free Imperial City of Kempten |
E890681
|
entity |
| Predicate | circleOfEmpire |
P179623
|
FINISHED |
| Object | Swabian Circle |
—
|
NE NERFINISHED |
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: Swabian Circle | Statement: [Free Imperial City of Kempten, circleOfEmpire, Swabian Circle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: circleOfEmpire Context triple: [Free Imperial City of Kempten, circleOfEmpire, Swabian Circle]
-
A.
originatingEmpire
Indicates the empire from which an entity, such as a person, object, or event, originally comes or was first established.
-
B.
realmConqueredBy
Indicates that a particular realm or territory has been taken over and brought under the control of a specified conqueror.
-
C.
imaginaryEmpire
Indicates a relationship where an entity rules over or belongs to an empire that exists only in imagination, fiction, or conceptual thought rather than in reality.
-
D.
governingEmpire
Indicates that one entity serves as the ruling imperial power that controls or governs another entity.
-
E.
realmCenter
Indicates that one entity serves as the central or focal point of a given realm, domain, or spatial region in relation to another entity.
- 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_69f349dabc008190a18999c26682ed47 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7232a16a081909b775efc60b45244 |
completed | May 3, 2026, 10:27 a.m. |
| PD | Predicate disambiguation | batch_69f72157af108190880317a62e634bb0 |
completed | May 3, 2026, 10:20 a.m. |
| PDg | Predicate description generation | batch_69f7221bc57c819085c1464a45e61b2f |
completed | May 3, 2026, 10:23 a.m. |
Created at: May 1, 2026, 2:05 a.m.