Triple
T32362703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl der Dicke |
E826906
|
entity |
| Predicate | HerrschaftsgebietUmfasste |
P44467
|
FINISHED |
| Object | Ostfrankenreich |
—
|
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: Ostfrankenreich | Statement: [Karl der Dicke, HerrschaftsgebietUmfasste, Ostfrankenreich]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HerrschaftsgebietUmfasste Context triple: [Karl der Dicke, HerrschaftsgebietUmfasste, Ostfrankenreich]
-
A.
historicalRegionGoverned
chosen
Indicates that a subject entity exercised governing authority over a particular historical region during a specified period.
-
B.
oversawArea
Indicates that one entity had supervisory or managerial responsibility over a particular area, region, or domain associated with another entity.
-
C.
feudalJurisdictionOver
Indicates that one entity holds legal and administrative authority or control over another entity within a feudal system.
-
D.
mainTerritoryOfInfluence
Indicates the primary geographic area where an entity exerts the most significant control, impact, or influence.
-
E.
occupiedRegion
Indicates that an entity has taken control of and is currently holding a specific geographic area or region.
- 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_69f34915a2588190bb3178f5ec2f48f4 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be9be6b48190b164c572650e8b95 |
completed | May 3, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:49 a.m.