Triple
T35068090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cake the Cat |
E1011786
|
entity |
| Predicate | genderSwappedCounterpartOf |
P21356
|
FINISHED |
| Object | Jake the Dog |
—
|
NE NERFINISHED |
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: Jake the Dog | Statement: [Cake the Cat, genderSwappedCounterpartOf, Jake the Dog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genderSwappedCounterpartOf Context triple: [Cake the Cat, genderSwappedCounterpartOf, Jake the Dog]
-
A.
femaleCounterpartOf
Indicates that one entity is the female equivalent or corresponding counterpart of another entity within a given role, relationship, or category.
-
B.
genderReversalOf
chosen
Indicates that one entity is a counterpart of another with the same role or characteristics but with the opposite gender.
-
C.
genderImplication
Indicates that one entity’s gender suggests, constrains, or determines the possible or likely gender of another entity.
-
D.
maleEquivalent
Indicates that one entity is the corresponding male counterpart or equivalent of another entity.
-
E.
genderTarget
Indicates that an action, message, or effect is specifically directed toward entities of a particular 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_69f76dd193108190af2528186f25b72a |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.