Triple
T31481503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abu al-Husayn |
E803155
|
entity |
| Predicate | associatedPersonDenomination |
P147195
|
FINISHED |
| Object | Sunni |
—
|
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: Sunni | Statement: [Abu al-Husayn, associatedPersonDenomination, Sunni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedPersonDenomination Context triple: [Abu al-Husayn, associatedPersonDenomination, Sunni]
-
A.
associatedPersonField
Indicates that there is a person linked or connected to the subject in a relevant or contextual way.
-
B.
associatedDenominationFamily
chosen
Indicates a relationship where one entity is linked to, or belongs within, a particular denomination family or broader denominational grouping.
-
C.
namedPersonAssociation
Indicates a relationship where one entity is associated with or identified by a specific personal name.
-
D.
associatedPersonNotability
Indicates that the relationship specifies the notable characteristic, achievement, or reason for prominence of the associated person.
-
E.
associatedPeopleStatus
Indicates the role, condition, or standing of people who are connected or linked to a given entity or event.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:32 p.m.