Triple
T13392826
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Julius Rosenberg and Ethel Rosenberg |
E319617
|
entity |
| Predicate | caseBecame |
P6579
|
FINISHED |
| Object | major Cold War controversy |
—
|
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: major Cold War controversy | Statement: [Julius Rosenberg and Ethel Rosenberg, caseBecame, major Cold War controversy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: caseBecame Context triple: [Julius Rosenberg and Ethel Rosenberg, caseBecame, major Cold War controversy]
-
A.
became
chosen
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
B.
centralToCase
Indicates that something plays a pivotal or essential role in determining the outcome or understanding of a particular case.
-
C.
caseLocation
Indicates the specific place or jurisdiction in which a case or legal matter is situated, filed, or adjudicated.
-
D.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
E.
caseHeBrought
Indicates that a male subject initiated and brought a legal case or lawsuit against another party.
- 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_69d806b886bc8190b676e7768b8e01c5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dba0d74e5881909828854bba7d9a87 |
completed | April 12, 2026, 1:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03189908190a784a2755f8d81e1 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:34 p.m.