Triple
T38071846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Winter Soldier |
E950604
|
entity |
| Predicate | underwentBrainwashingBy |
P195526
|
FINISHED |
| Object | Hydra |
—
|
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: Hydra | Statement: [The Winter Soldier, underwentBrainwashingBy, Hydra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: underwentBrainwashingBy Context triple: [The Winter Soldier, underwentBrainwashingBy, Hydra]
-
A.
wasGroomedAs
Indicates that one entity was raised, trained, or prepared by another for a particular future role, position, or purpose.
-
B.
confessedUnderInfluenceOf
Indicates that an individual made a confession while under the influence of some external factor (such as drugs, alcohol, coercion, or psychological pressure) that may have affected their free will or judgment.
-
C.
erasesMemoriesOf
Indicates that one entity causes the memories of another entity to be removed or wiped out.
-
D.
resultOfTorture
Indicates that something occurs as a direct consequence or outcome of an act of torture.
-
E.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
- 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_69f76f02a6c48190a94f3c0b3ee90cf2 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
| PDg | Predicate description generation | batch_69fdd5faea908190a17d77e050362ef5 |
completed | May 8, 2026, 12:24 p.m. |
Created at: May 3, 2026, 4:21 p.m.