Triple
T11975685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherelle Griner |
E285033
|
entity |
| Predicate | partnerGender |
P32629
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Cherelle Griner, partnerGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partnerGender Context triple: [Cherelle Griner, partnerGender, female]
-
A.
spouseGender
chosen
Indicates the gender of a person’s spouse in a marital relationship.
-
B.
plugGender
Indicates that one entity’s connector has a specified gender (e.g., male, female, neutral) in relation to another connector or interface.
-
C.
genderTarget
Indicates that an action, message, or effect is specifically directed toward entities of a particular gender.
-
D.
lifePartnerType
Indicates the type or category of a person’s life partner in a long-term or committed relationship.
-
E.
playsGender
Indicates that one entity performs or assumes a particular gender role or identity in a given context.
- 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_69d6ab2eaeb881909f7914758f859413 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903926690819090e7ce982f103457 |
completed | April 10, 2026, 2:05 p.m. |
| PD | Predicate disambiguation | batch_69d8bb40f30c8190a0e0719bd67542bf |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:46 p.m.