Triple
T34818844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vera Stravinsky |
E1003710
|
entity |
| Predicate | relationshipStartWithIgorStravinsky |
P194490
|
FINISHED |
| Object | early 1920s |
—
|
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: early 1920s | Statement: [Vera Stravinsky, relationshipStartWithIgorStravinsky, early 1920s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relationshipStartWithIgorStravinsky Context triple: [Vera Stravinsky, relationshipStartWithIgorStravinsky, early 1920s]
-
A.
roleInIgorStravinskyLife
Indicates the specific role or involvement an entity had in Igor Stravinsky’s life.
-
B.
marriedToIgorStravinskyFrom
chosen
Indicates that an entity was married to Igor Stravinsky starting from a specified point in time.
-
C.
yearOfCollaborationWithShostakovich
Indicates the specific year in which an entity collaborated with Shostakovich.
-
D.
startOfAssociationWithTchaikovsky
Indicates the point in time when an entity first began an association or collaborative relationship with Tchaikovsky.
-
E.
isRelatedWorkOfComposer
Indicates that one work is associated with or connected to a particular composer, typically as a composition created by that composer.
- 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_69f76db717088190811b4e744610f37d |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fd7aac8190873077e63873aa72 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4 p.m.