Triple
T34267558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | muxe |
E879213
|
entity |
| Predicate | embodiesGenderExpression |
P48674
|
FINISHED |
| Object | feminine |
—
|
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: feminine | Statement: [muxe, embodiesGenderExpression, feminine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embodiesGenderExpression Context triple: [muxe, embodiesGenderExpression, feminine]
-
A.
hasGenderIdentity
Indicates that an entity identifies with or experiences a particular gender.
-
B.
publiclyIdentifiesAs
Indicates that an entity openly declares or presents themself to others as having a particular identity or role.
-
C.
genderVariation
Indicates that one entity is a variant or alternative form of another entity that differs specifically in grammatical or biological gender.
-
D.
genderVariant
chosen
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
-
E.
genderVariants
Indicates that one entity is a gender-related variant or alternative form of another (e.g., masculine/feminine/neuter versions of the same base entity).
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f71362f1448190985a80ce7af475cb |
completed | May 3, 2026, 9:20 a.m. |
| PD | Predicate disambiguation | batch_69f7127884388190884f23d181a65d19 |
completed | May 3, 2026, 9:16 a.m. |
Created at: May 1, 2026, 1:56 a.m.