Triple
T12615901
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fields Institute for Research in Mathematical Sciences |
E301250
|
entity |
| Predicate | movedToTorontoIn |
P100317
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Fields Institute for Research in Mathematical Sciences, movedToTorontoIn, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedToTorontoIn Context triple: [Fields Institute for Research in Mathematical Sciences, movedToTorontoIn, 1995]
-
A.
movedToLosAngeles
Indicates that an entity changed their place of residence or primary location to Los Angeles.
-
B.
immigratedTo
Indicates that an entity moved from its country of origin to live permanently in another specified country or region.
-
C.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
D.
cityAfterRelocation
chosen
Indicates the city where an entity is located after it has been moved or relocated from a previous place.
-
E.
locatedInOldCity
Indicates that an entity is situated within the boundaries of an old or historic part of a city.
- 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_69d7bdeaf49c8190b13800111fa77ea3 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9617b07ec8190b714f04ae6654060 |
completed | April 10, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69d960b195108190ac25bd95e644ace4 |
completed | April 10, 2026, 8:42 p.m. |
Created at: April 9, 2026, 5:12 p.m.