Triple
T17107563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Husayn I ibn Ali |
E415139
|
entity |
| Predicate | dynastyFoundedIn |
P125955
|
FINISHED |
| Object | 1705 |
—
|
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: 1705 | Statement: [Husayn I ibn Ali, dynastyFoundedIn, 1705]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dynastyFoundedIn Context triple: [Husayn I ibn Ali, dynastyFoundedIn, 1705]
-
A.
dynastyFoundedBecame
Indicates that an entity founded a dynasty and subsequently became its ruler or central figure.
-
B.
dynastyFoundedRuledPeriod
Indicates that a particular dynasty was founded and held ruling authority during a specified historical time period.
-
C.
foundingDynastyOf
Indicates that a particular dynasty is the original founding ruling house or lineage of a specified political entity, state, or realm.
-
D.
currentDynastyFoundedYear
Indicates the year in which the currently ruling dynasty was established or came into power.
-
E.
dynastyFoundedRuledRegion
Indicates that a particular dynasty was established and exercised ruling authority over a specified region.
- 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_69d886cfc8e88190b05ba466edd35591 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dc280b0c8190b9e620b90e0d4b40 |
completed | April 18, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:35 a.m.