Triple
T31069831
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Abu Bakar |
E791785
|
entity |
| Predicate | hasDynasticReligion |
P21571
|
FINISHED |
| Object | Islam |
—
|
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: Islam | Statement: [House of Abu Bakar, hasDynasticReligion, Islam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDynasticReligion Context triple: [House of Abu Bakar, hasDynasticReligion, Islam]
-
A.
dynasticReligion
chosen
Indicates that a dynasty or ruling family is associated with, practices, or is characterized by a particular religion.
-
B.
hasPrimaryReligionOfRulers
Indicates that the specified religion is the main or official faith practiced or endorsed by the rulers of an entity.
-
C.
dynasticReligionRole
Indicates a relationship where an entity holds a religious office, function, or status specifically within the context of a ruling dynasty or hereditary line.
-
D.
hasMajorDynasty
Indicates that an entity (such as a region, state, or historical period) is associated with or ruled by a particular major dynasty.
-
E.
dominantReligionLegacy
Indicates that a historically dominant religion has left a lasting influence or heritage on a society, culture, or region.
- 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_69f224cc0c5c81908404f087bff92997 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f697eabb048190bc01a830f14942c6 |
completed | May 3, 2026, 12:33 a.m. |
| PD | Predicate disambiguation | batch_69f69664142c8190bc695501056b0236 |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:01 p.m.