Triple
T21258909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mikhailovskoye estate |
E523943
|
entity |
| Predicate | reasonForResidence |
P128720
|
FINISHED |
| Object | Pushkin’s exile from St. Petersburg |
—
|
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: Pushkin’s exile from St. Petersburg | Statement: [Mikhailovskoye estate, reasonForResidence, Pushkin’s exile from St. Petersburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForResidence Context triple: [Mikhailovskoye estate, reasonForResidence, Pushkin’s exile from St. Petersburg]
-
A.
reasonForHabitation
chosen
Indicates that an entity resides or inhabits a place for a specified reason or purpose.
-
B.
intendedResidence
Indicates that one entity is designated or planned to serve as the place where another entity will live or reside.
-
C.
otherResidence
Indicates that an entity has an additional or alternative place of residence beyond its primary home.
-
D.
likelyResidence
Indicates that an entity is probably located at, lives at, or is most commonly associated with a particular place of residence.
-
E.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e477d08190be17ad5384d69a80 |
completed | April 21, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69e5f61239708190ab7b3c83ae848a0d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 3:59 p.m.