Triple
T22700514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sakharam |
E561307
|
entity |
| Predicate | treatsWomenAs |
P109101
|
FINISHED |
| Object | Temporary partners |
—
|
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: Temporary partners | Statement: [Sakharam, treatsWomenAs, Temporary partners]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: treatsWomenAs Context triple: [Sakharam, treatsWomenAs, Temporary partners]
-
A.
treatsHumansAs
chosen
Indicates how one entity regards or behaves toward humans, characterizing them in a particular way (e.g., as equals, tools, resources, or threats).
-
B.
genderStereotypingRecognizedAs
Indicates that a particular belief, behavior, or representation is acknowledged or classified as a form of gender stereotyping.
-
C.
femaleHas
Indicates that a specified entity is female or possesses a female gender attribute in relation to another entity or context.
-
D.
femaleBehavior
Indicates that the behavior or actions being referred to are characteristic of, or typically associated with, females in the given context.
-
E.
femaleAddressedAs
Indicates that a female individual is referred to or addressed by a particular name, title, or form of address.
- 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_69e2454e615481909c177440be559d2c |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178ca683c81909f6b4e26b85c99c1 |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:15 p.m.