Triple
T1779484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingdom of Bavaria |
E39255
|
entity |
| Predicate | capitalCityFrom |
P30707
|
FINISHED |
| Object | Munich, from 1806 to 1918 |
—
|
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: Munich, from 1806 to 1918 | Statement: [Kingdom of Bavaria, capitalCityFrom, Munich, from 1806 to 1918]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capitalCityFrom Context triple: [Kingdom of Bavaria, capitalCityFrom, Munich, from 1806 to 1918]
-
A.
capitalCityOfCountry
Indicates that a city serves as the official capital of a specified country.
-
B.
capitalOfFrom
chosen
Indicates that a city serves or served as the capital of a specified political entity during a particular time or from a particular source context.
-
C.
countryCapitalOf
Indicates that a country serves as the capital location for a specified political or geographic entity.
-
D.
hostsCapitalOf
Indicates that one location serves as the capital city of another administrative or political entity.
-
E.
regionCapital
Indicates that one entity is the capital city or administrative center of a specified 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab74dc9d1481908084ef07872a71f8 |
completed | March 7, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69aa61cf3ca881908641fd73ce2f7c9d |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.