Triple
T17162598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fakhr al-Dawla |
E416516
|
entity |
| Predicate | ethnoCulturalBackground |
P56388
|
FINISHED |
| Object | Daylamite-associated ruling elite |
—
|
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: Daylamite-associated ruling elite | Statement: [Fakhr al-Dawla, ethnoCulturalBackground, Daylamite-associated ruling elite]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ethnoCulturalBackground Context triple: [Fakhr al-Dawla, ethnoCulturalBackground, Daylamite-associated ruling elite]
-
A.
ethnicOrigin
Indicates the relationship where an entity is associated with a particular ethnic group or ancestry.
-
B.
cultureOfOrigin
chosen
Indicates the cultural background or tradition from which an entity originates or is derived.
-
C.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
D.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
-
E.
ethnicityInTradition
Indicates that a particular ethnicity is associated with, represented in, or plays a role within a specified cultural or religious tradition.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f91316108190b0d856d6fa5cd509 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.