Triple
T22349311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polina Alexandrovna |
E552485
|
entity |
| Predicate | relationshipTypeWithAlexeiIvanovich |
P147874
|
FINISHED |
| Object | romantic tension |
—
|
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: romantic tension | Statement: [Polina Alexandrovna, relationshipTypeWithAlexeiIvanovich, romantic tension]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipTypeWithAlexeiIvanovich Context triple: [Polina Alexandrovna, relationshipTypeWithAlexeiIvanovich, romantic tension]
-
A.
relationshipToPolinaAlexandrovna
Indicates the specific type of personal or social relationship that one entity has with Polina Alexandrovna.
-
B.
relationshipToTatyanaLarina
Indicates the specific personal or social connection that an entity has to Tatyana Larina.
-
C.
relationshipToPavelVlasov
Indicates the nature or type of relationship an entity has with Pavel Vlasov.
-
D.
relationshipTypeWithPavel Chichikov
Indicates the specific type or nature of the relationship that an entity has with Pavel Chichikov.
-
E.
relationshipToOnegin
Indicates the specific interpersonal or familial relationship that one entity has to the person named Onegin.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f1579ad6708190ba4af97a02d0758d |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:43 p.m.