Triple
T26228339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Samantha Elauf |
E655958
|
entity |
| Predicate | reasonForEmploymentDenial |
P6667
|
FINISHED |
| Object | wearing a hijab |
—
|
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: wearing a hijab | Statement: [Samantha Elauf, reasonForEmploymentDenial, wearing a hijab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForEmploymentDenial Context triple: [Samantha Elauf, reasonForEmploymentDenial, wearing a hijab]
-
A.
reasonForDecline
chosen
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
B.
resultOfDenial
Indicates that something occurs or exists as a consequence of a prior denial event or refusal.
-
C.
legalStatusDenied
Indicates that an entity has been refused or not granted a particular legal status or recognition.
-
D.
reasonForDismissal
Indicates the cause or justification for which an entity (such as a person, case, or item) was dismissed, terminated, or removed.
-
E.
designationReason
Indicates the reason or justification for assigning a particular designation or status to an 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 26, 2026, 8:58 p.m.