Triple
T35200340
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Surpassing Certainty |
E1016379
|
entity |
| Predicate | hasAuthorGenderIdentity |
P43613
|
FINISHED |
| Object | transgender woman |
—
|
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 woman | Statement: [Surpassing Certainty, hasAuthorGenderIdentity, transgender woman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorGenderIdentity Context triple: [Surpassing Certainty, hasAuthorGenderIdentity, transgender woman]
-
A.
hasAuthorGender
Indicates that an entity (such as a work or publication) is associated with an author of a specified gender.
-
B.
hasGenderIdentity
chosen
Indicates that an entity identifies with or experiences a particular gender.
-
C.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
D.
genderOfPseudonym
Indicates the gender associated with a given pseudonym or pen name.
-
E.
hasGenderRole
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: May 3, 2026, 4:02 p.m.