Triple
T32540715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kaiser und König (Austria-Hungary) |
E831705
|
entity |
| Predicate | HungarianCoronationCity |
P154814
|
FINISHED |
| Object | Budapest |
—
|
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: Budapest | Statement: [Kaiser und König (Austria-Hungary), HungarianCoronationCity, Budapest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HungarianCoronationCity Context triple: [Kaiser und König (Austria-Hungary), HungarianCoronationCity, Budapest]
-
A.
wasRoyalCityOf
chosen
Indicates that a city formerly served as the royal or principal city (such as a capital or main seat of power) of a specified kingdom, dynasty, or ruling authority.
-
B.
reignAsKingOfHungaryEnd
Indicates the time or event at which an entity’s reign as King of Hungary comes to an end.
-
C.
papalCoronationCity
Indicates the city where a papal coronation took place.
-
D.
countryDuringKingdomOfHungary
Indicates that a country existed within the territorial or political bounds of the Kingdom of Hungary during a specified historical period.
-
E.
predecessorAsKingOfHungary
Indicates that one person previously held the position of King of Hungary immediately before another person.
- 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_69f34924b1cc8190ad3aca0c0f012a7e |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c57e3ea48190a075c1165db4eecd |
completed | May 3, 2026, 3:48 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2a14b081908162923dfbf0a6f4 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:02 a.m.