Triple
T36182429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Binx |
E1046751
|
entity |
| Predicate | genderAsHuman |
P185385
|
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: [Binx, genderAsHuman, male]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderAsHuman Context triple: [Binx, genderAsHuman, male]
-
A.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
B.
genderCustom
Indicates that an entity has a user-specified or non-standard gender designation beyond predefined gender categories.
-
C.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
D.
genderRule
Indicates a rule or constraint that determines how gender-related properties or classifications should be assigned or interpreted in a given context.
-
E.
genderVariant
Indicates that an entity’s gender identity or expression differs from traditional or expected norms associated with their assigned sex or gender.
- 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_69f76e3c1b10819081fc7a807a71cf84 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
| PDg | Predicate description generation | batch_69f7be9b9ab481908328e0e8d8ac73d4 |
completed | May 3, 2026, 9:31 p.m. |
Created at: May 3, 2026, 4:08 p.m.