Triple
T20049104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 志忠 |
E499143
|
entity |
| Predicate | typicalGenderRole |
P69451
|
FINISHED |
| Object | male |
—
|
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: male | Statement: [志忠, typicalGenderRole, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGenderRole Context triple: [志忠, typicalGenderRole, male]
-
A.
sexualRole
Indicates the specific sexual function, position, or behavioral role one entity assumes in a sexual interaction or relationship with another.
-
B.
hasTypicalGenderAssociation
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
C.
hasGenderRole
chosen
Indicates that an entity is associated with, or expected to perform, a particular socially defined gender-based role or set of behaviors.
-
D.
genderNorms
Indicates socially constructed expectations or rules about how individuals should behave, appear, or identify based on their perceived gender.
-
E.
genderRoleSignificance
Indicates the extent to which gender roles are considered important, influential, or defining within a given relationship, context, or interaction.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6632cccb481908278c8b2930a8c26 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:37 p.m.