Triple
T38695120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pathan |
E949975
|
entity |
| Predicate | sometimesConsideredPejorative |
P137719
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Pathan, sometimesConsideredPejorative, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sometimesConsideredPejorative Context triple: [Pathan, sometimesConsideredPejorative, yes]
-
A.
hasPejorativeUsage
chosen
Indicates that the referenced term or expression is used in a disparaging, derogatory, or negative manner toward its subject.
-
B.
hasPejorativeOrigin
Indicates that the referenced term, label, or expression originates from a disparaging, derogatory, or contemptuous usage or context.
-
C.
hasPejorativeName
Indicates that an entity is referred to by a name or label that carries a negative, derogatory, or disparaging connotation.
-
D.
sometimesCriticizedFor
Indicates that an entity is on occasion the target of criticism for a particular reason, behavior, or attribute.
-
E.
hasNegativeConnotation
Indicates that the referenced term, expression, or association carries an unfavorable, disapproving, or undesirable implication.
- 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_69f76f0124408190bb39c3040734846b |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fcdfbc71c481908ba7f87907b17782 |
completed | May 7, 2026, 6:53 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe580b8819087f143596b2c79c0 |
completed | May 7, 2026, 6:37 p.m. |
Created at: May 3, 2026, 4:33 p.m.