Triple
T16834094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tribulation Periwinkle |
E409225
|
entity |
| Predicate | genderInText |
P59205
|
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: [Tribulation Periwinkle, genderInText, female]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderInText Context triple: [Tribulation Periwinkle, genderInText, female]
-
A.
genderDivision
Indicates a relationship where roles, responsibilities, or categories are separated or distinguished based on gender.
-
B.
hasGenderInText
chosen
Indicates that a specified gender is explicitly mentioned or assigned to an entity within a given text.
-
C.
genderConfiguration
Indicates how the genders of the involved entities are arranged or combined within a particular relationship or context.
-
D.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
-
E.
genderOfName
Indicates the gender typically associated with a given name.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b31981ac8190bbd9720efe842778 |
completed | April 18, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69e32b87b4248190aaddb05e88452356 |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:23 a.m.