Triple
T9238261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bysshe |
E221990
|
entity |
| Predicate | givenNameGenderAssociation |
P34349
|
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: [Bysshe, givenNameGenderAssociation, masculine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givenNameGenderAssociation Context triple: [Bysshe, givenNameGenderAssociation, masculine]
-
A.
namedForGender
Indicates that one entity is named in a way that reflects or is derived from a particular gender or gender-related characteristic of another entity.
-
B.
hasGenderOfPerson
Indicates that a person is associated with a specific gender classification.
-
C.
hasTypicalGenderAssociation
chosen
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
D.
genderOfEponym
Indicates the gender of the person after whom something (such as a place, object, or concept) is named.
-
E.
genderSignificance
Indicates the relevance or impact that an entity’s gender has within a particular context, relationship, or interpretation.
- 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_69ca83ee26cc81909ac624e190597d6d |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69ccf09f9e908190801fe114c5e63984 |
completed | April 1, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69cc7a4765648190aa9445c4a22dc471 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:30 p.m.