Triple
T8081810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivan Galamian |
E188632
|
entity |
| Predicate | yearMovedTo |
P1741
|
FINISHED |
| Object | United States of America, 1937 |
—
|
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: United States of America, 1937 | Statement: [Ivan Galamian, yearMovedTo, United States of America, 1937]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: yearMovedTo Context triple: [Ivan Galamian, yearMovedTo, United States of America, 1937]
-
A.
headquartersMovedOn
Indicates that the location of an entity’s headquarters changed on a specific date or point in time.
-
B.
relocationYear
chosen
Indicates the year in which an entity was moved or transferred from one location to another.
-
C.
relocatedTo
Indicates that an entity has moved or been transferred from its previous location to a new specified location.
-
D.
settledInYear
Indicates the specific calendar year in which an entity became established, inhabited, or formally settled in a particular place or status.
-
E.
dateCapitalMoved
Indicates the date on which a capital city was officially relocated from one place to another.
- 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_69ca82b662e88190b9323daab8c28a21 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb40a699388190a5b8e26524ae43e5 |
completed | March 31, 2026, 3:33 a.m. |
| PD | Predicate disambiguation | batch_69cb049f1614819087360d1a4c6f0faa |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:28 p.m.