Triple
T31389003
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tatiana Riabouchinska |
E800678
|
entity |
| Predicate | peerGroup |
P171681
|
FINISHED |
| Object | Irina Baronova |
—
|
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: Irina Baronova | Statement: [Tatiana Riabouchinska, peerGroup, Irina Baronova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: peerGroup Context triple: [Tatiana Riabouchinska, peerGroup, Irina Baronova]
-
A.
participantGroup
Indicates a relationship in which a set or group of entities jointly participate in a common event, activity, or interaction.
-
B.
groups
Indicates that one entity organizes, clusters, or associates multiple entities together as members of a collective set or category.
-
C.
memberOf
Indicates that an entity belongs to, is part of, or is a constituent of a larger group, organization, or collection.
-
D.
positionGroup
Indicates a grouping relationship where multiple positions or roles are collectively associated or organized under a common group.
-
E.
formedGroup
Indicates that multiple entities have come together to create or establish a group or collective unit.
- 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_69f224e9d7048190b0cc20f9071bd3e4 |
completed | April 29, 2026, 3:34 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 9:19 p.m.