Triple
T29842539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Moor (Petrushka) |
E757839
|
entity |
| Predicate | competesForAffectionWith |
P176746
|
FINISHED |
| Object | Petrushka (character) |
—
|
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: Petrushka (character) | Statement: [The Moor (Petrushka), competesForAffectionWith, Petrushka (character)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competesForAffectionWith Context triple: [The Moor (Petrushka), competesForAffectionWith, Petrushka (character)]
-
A.
affectionReciprocated
Indicates that feelings of affection expressed by one entity toward another are mutually returned by the other entity.
-
B.
siblingRival
Indicates a relationship where two siblings are in competition or conflict with each other.
-
C.
objectOfAffectionFor
Indicates that one entity is the target or recipient of another entity’s romantic or affectionate feelings.
-
D.
hasPetRival
Indicates that one entity has a pet that is in a rivalry relationship with another entity's pet.
-
E.
isEnviedBy
Indicates that one entity is the object of another entity’s envy or jealousy.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6e6029a10819098ff21f58079e70e |
completed | May 3, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d5e8188190b1e1c2e5d1b77031 |
completed | May 3, 2026, 5:57 a.m. |
| PDg | Predicate description generation | batch_69f6e60109648190947a64ca4ce81a3a |
completed | May 3, 2026, 6:06 a.m. |
Created at: April 29, 2026, 5:40 p.m.