Triple
T2133146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Ride (lunar crater) |
E46587
|
entity |
| Predicate | hasEponymGender |
P27732
|
FINISHED |
| Object | female |
—
|
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: female | Statement: [Sally Ride (lunar crater), hasEponymGender, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEponymGender Context triple: [Sally Ride (lunar crater), hasEponymGender, female]
-
A.
namedForGender
chosen
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.
hasFemaleEquivalent
Indicates that one entity serves as the female counterpart or equivalent of another entity.
-
C.
creatorSexOrGender
Indicates that the specified sex or gender is the sex or gender of the creator of the referenced work or entity.
-
D.
hasTypicalGenderAssociation
Indicates that one entity is commonly or culturally associated with a particular gender more than with other genders.
-
E.
hasAuthorGender
Indicates that an entity (such as a work or publication) is associated with an author of a specified gender.
- 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_69a88a1626548190ae59a5028c3baa8e |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbba0c42c8190ab3ce4bbf1531ee1 |
completed | March 7, 2026, 5:46 a.m. |
| PD | Predicate disambiguation | batch_69abb7bf56e481909b0f497d238451cc |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:44 p.m.