Triple
T9966722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Giles |
E195700
|
entity |
| Predicate | facesDiscriminationContext |
P41973
|
FINISHED |
| Object | homophobia |
—
|
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: homophobia | Statement: [Giles, facesDiscriminationContext, homophobia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: facesDiscriminationContext Context triple: [Giles, facesDiscriminationContext, homophobia]
-
A.
typeOfDiscrimination
chosen
Indicates a relationship where one party is subjected to a specific kind or category of discriminatory treatment by another party or within a given context.
-
B.
faceValueType
Indicates the type or category of a financial instrument’s face (nominal) value, such as how that value is defined or represented.
-
C.
faceType
Indicates the specific shape or structural category of a face that an entity possesses or is characterized by.
-
D.
facesChallenge
Indicates that an entity is confronted with a difficulty, obstacle, or demanding situation that must be dealt with or overcome.
-
E.
discriminationStatus
Indicates whether an entity is subject to, engaged in, or affected by discriminatory treatment based on protected or distinguishing characteristics.
- 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_69ca82ebd1288190912f9e4482d1fa35 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb71dc50081909329722dc087c9f6 |
completed | April 2, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69cd1d9ae19c819099fb3635e57c79be |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:47 p.m.