Triple
T23510191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zia |
E572397
|
entity |
| Predicate | hasAlternativeGenderUsage |
P152652
|
FINISHED |
| Object | masculine |
—
|
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: masculine | Statement: [Zia, hasAlternativeGenderUsage, masculine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternativeGenderUsage Context triple: [Zia, hasAlternativeGenderUsage, masculine]
-
A.
hasGenderVariant
Indicates that one entity is a gender-specific form or variant of another entity.
-
B.
hasGenderNeutrality
Indicates that something (such as a term, form, or expression) is neutral with respect to gender and does not specify or imply any particular gender.
-
C.
hasGenderDistinction
Indicates that a relationship, classification, or linguistic form differentiates entities based on gender categories.
-
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.
hasFeminineFormInSomeLanguages
Indicates that the referenced entity has a distinct feminine grammatical or lexical form in at least one language.
- 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_69e245b5e4208190bac8a6509867e394 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a90455f0819092b37c69d7e73c43 |
completed | April 29, 2026, 6:45 a.m. |
| PD | Predicate disambiguation | batch_69f0621165c08190a0b27b1319733959 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:07 p.m.