Triple
T33379726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bihar |
E854737
|
entity |
| Predicate | wasCountyOf |
P49034
|
FINISHED |
| Object | Kingdom of Hungary |
—
|
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: Kingdom of Hungary | Statement: [Bihar, wasCountyOf, Kingdom of Hungary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasCountyOf Context triple: [Bihar, wasCountyOf, Kingdom of Hungary]
-
A.
wasCounty
chosen
Indicates that an entity previously held the status or role of a county in relation to a larger administrative or political unit.
-
B.
isNamedCountyOf
Indicates that a county bears a specific official name within a given jurisdiction or context.
-
C.
inCounty
Indicates that one entity is geographically or administratively located within the boundaries of a specified county.
-
D.
hasCountySeatOfParentCounty
Indicates that a location serves as the county seat (administrative center) for the county that is the parent of another referenced entity.
-
E.
hasCountySeatOf
Indicates that a place serves as the administrative county seat (capital) of a specified county.
- 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_69f3496ca10c8190908640d18fa00832 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:35 a.m.