Triple
T35308185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jayda al-Sindiyya |
E1019693
|
entity |
| Predicate | primaryRoleInSources |
P134117
|
FINISHED |
| Object | maternalFigureOfZayd ibn Ali |
—
|
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: maternalFigureOfZayd ibn Ali | Statement: [Jayda al-Sindiyya, primaryRoleInSources, maternalFigureOfZayd ibn Ali]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryRoleInSources Context triple: [Jayda al-Sindiyya, primaryRoleInSources, maternalFigureOfZayd ibn Ali]
-
A.
primaryRoleFor
Indicates that one entity serves as the main or most important role or function for another entity.
-
B.
principalRoleIn
chosen
Indicates that an entity holds the primary or leading role in a particular context, activity, or relationship.
-
C.
primaryContributionOf
Indicates that one entity is the main or most significant contribution made by another entity.
-
D.
primaryRoleInHierarchy
Indicates that one entity holds the main or most important role or position within a defined hierarchy relative to another entity.
-
E.
primaryAdministrativeRole
Indicates that an entity holds the main or most significant administrative position or function in relation to another entity.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0324d08190ac5b610cc0f6a38c |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:03 p.m.