Triple
T1638163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Müller |
E35404
|
entity |
| Predicate | hasTypicalGenderUsage |
P15656
|
FINISHED |
| Object | used for all genders |
—
|
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: used for all genders | Statement: [Müller, hasTypicalGenderUsage, used for all genders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalGenderUsage Context triple: [Müller, hasTypicalGenderUsage, used for all genders]
-
A.
genderUsage
chosen
Indicates how a particular gender is applied, referenced, or treated within a given context or system.
-
B.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
C.
hasGenderFocus
Indicates that something is specifically concerned with, oriented toward, or primarily addressing a particular gender or gender-related issues.
-
D.
hasGrammaticalGender
Indicates that one entity assigns or possesses a specific grammatical gender in relation to another entity (such as a word, phrase, or linguistic unit).
-
E.
hasNeutralPronoun
Indicates that an entity is referred to using a gender-neutral pronoun.
- 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_69a88604618c81908b41f6429c431eb6 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a96083e7308190abbf025fe8e43abb |
completed | March 5, 2026, 10:52 a.m. |
| PD | Predicate disambiguation | batch_69a907cac610819083cafd4396b6d66c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.