Triple
T178463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mister Speaker |
E3628
|
entity |
| Predicate | genderSpecificTo |
P72
|
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: [Mister Speaker, genderSpecificTo, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderSpecificTo Context triple: [Mister Speaker, genderSpecificTo, male]
-
A.
genderCategories
Indicates the classification of an entity into one or more gender-related categories or identities.
-
B.
sexOrGender
chosen
Indicates that one entity has a specified biological sex or socially constructed gender identity.
-
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.
hasNumberOfGenders
Indicates the relationship that specifies how many distinct genders are associated with or recognized for a given 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_69a25374990081909766d30c79a18e0e |
completed | Feb. 28, 2026, 2:31 a.m. |
| NER | Named-entity recognition | batch_69a258fe7bb08190a56f4a54cadd2fef |
completed | Feb. 28, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69a2566b53d481909c0ed40dd3719e8c |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:39 a.m.