Triple
T20649349
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nure Sufi Bey |
E507444
|
entity |
| Predicate | governmentFormFounded |
P140907
|
FINISHED |
| Object | hereditary beylik |
—
|
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: hereditary beylik | Statement: [Nure Sufi Bey, governmentFormFounded, hereditary beylik]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentFormFounded Context triple: [Nure Sufi Bey, governmentFormFounded, hereditary beylik]
-
A.
stateTypeFounded
Indicates that a particular type or category of state was established or came into existence at a certain point or by a certain founding event.
-
B.
governingBodyFoundedIn
Indicates that a governing body was established or came into official existence in a specified year or time period.
-
C.
coFoundedIn
Indicates that two or more entities jointly founded something (such as an organization or company) in a specific place or at a specific time.
-
D.
politicalEntityFounded
Indicates that one political entity established or created another political entity at a specific point in time.
-
E.
organizationTypeFounded
Indicates the type or category of organization that was established or created in a founding event.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6af2076b48190b9c8afb4eac65f46 |
completed | April 20, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69e5c3caef50819093c8159fe8d6435b |
completed | April 20, 2026, 6:12 a.m. |
Created at: April 16, 2026, 11:43 a.m.