Triple
T9356896
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | In One Person |
E225161
|
entity |
| Predicate | exploresGenderIdentity |
P88127
|
FINISHED |
| Object | transgender identity |
—
|
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: transgender identity | Statement: [In One Person, exploresGenderIdentity, transgender identity]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exploresGenderIdentity Context triple: [In One Person, exploresGenderIdentity, transgender identity]
-
A.
hasGenderIdentity
Indicates that an entity identifies with or experiences a particular gender.
-
B.
protagonistGenderIdentity
Indicates the gender identity attributed to or expressed by the protagonist in a given context.
-
C.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
-
D.
sexOrGender
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
E.
genderPracticeVariesBy
Indicates that the way gender is expressed, understood, or practiced differs depending on the specific context, group, or setting involved.
- F. None of above. chosen
Provenance (4 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_69ca842abfd48190949d71c3b86eeba8 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd4fee9d4c8190a7d121c9487ccca2 |
completed | April 1, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69cc7a68ab9481909f97cb70764697cc |
completed | April 1, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69cc955a38108190b602d1e73725f11b |
completed | April 1, 2026, 3:47 a.m. |
Created at: March 30, 2026, 7:42 p.m.