Triple
T33553891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaika |
E859412
|
entity |
| Predicate | usedByPersonFullName |
P1480
|
FINISHED |
| Object | Valentina Vladimirovna Tereshkova |
—
|
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: Valentina Vladimirovna Tereshkova | Statement: [Chaika, usedByPersonFullName, Valentina Vladimirovna Tereshkova]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedByPersonFullName Context triple: [Chaika, usedByPersonFullName, Valentina Vladimirovna Tereshkova]
-
A.
usedByPerson
chosen
Indicates that something (such as an object, tool, or resource) is utilized or employed by a person.
-
B.
namedForPersonFullName
Indicates that an entity is named after a specific person, identified by that person’s full name.
-
C.
usedInFullNameOf
Indicates that one entity (such as a word, name part, or title) is used as a component within the complete formal name of another entity.
-
D.
bearerPersonalName
Indicates that a personal name is borne or held by a particular entity (the bearer).
-
E.
fullName
Indicates that an entity has a complete personal name, typically combining given name(s) and family name into a single string.
- 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_69f3497b2b68819093207971b5e13dc8 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd09840ea88190a2e6d7e577ade717 |
completed | May 7, 2026, 9:52 p.m. |
| PD | Predicate disambiguation | batch_69fd064c49988190afadddbd04d7cb94 |
completed | May 7, 2026, 9:38 p.m. |
Created at: May 1, 2026, 1:40 a.m.