Triple
T21599371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Pevear and Larissa Volokhonsky |
E532992
|
entity |
| Predicate | collaborationMethod |
P42125
|
FINISHED |
| Object | bilingual co-translation process |
—
|
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: bilingual co-translation process | Statement: [Richard Pevear and Larissa Volokhonsky, collaborationMethod, bilingual co-translation process]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaborationMethod Context triple: [Richard Pevear and Larissa Volokhonsky, collaborationMethod, bilingual co-translation process]
-
A.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
B.
platformCollaboration
Indicates a collaborative relationship where multiple entities work together or integrate their efforts on or through a shared platform.
-
C.
collaborationAspect
chosen
Indicates a specific characteristic, dimension, or feature of how entities collaborate or work together.
-
D.
collaborationModel
Indicates the type or structure of cooperative interaction or joint work established between entities.
-
E.
collaborationScope
Indicates the extent, boundaries, and areas of responsibility covered by a particular collaboration between entities.
- 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_69e0c46364608190a337dc8720dc2a35 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eefae4746c819090afe1d93fe9f175 |
completed | April 27, 2026, 5:57 a.m. |
| PD | Predicate disambiguation | batch_69e632109d048190b4ac3f14fe48d1a0 |
completed | April 20, 2026, 2:02 p.m. |
Created at: April 16, 2026, 6:32 p.m.