Triple
T5849472
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grand Duke of Russia |
E129991
|
entity |
| Predicate | continuedUseInExile |
P51870
|
FINISHED |
| Object | Romanov family in exile |
—
|
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: Romanov family in exile | Statement: [Grand Duke of Russia, continuedUseInExile, Romanov family in exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: continuedUseInExile Context triple: [Grand Duke of Russia, continuedUseInExile, Romanov family in exile]
-
A.
usedInExile
chosen
Indicates that something (such as a method, name, or identity) is employed or applied while an entity is in a state of exile.
-
B.
mainUseContinued
Indicates that the primary use or function of something persists or remains in effect over a subsequent period.
-
C.
subsequentUse
Indicates that one entity is used, applied, or consumed after another entity in time or sequence.
-
D.
continuedOnNetwork
Indicates that an entity (such as a show, series, or program) remained in production or broadcast on the same network beyond a given point in time.
-
E.
continuedBy
Indicates that one entity carries on, extends, or resumes the activity, process, or sequence initiated by another entity.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c03c9239e08190bff7ef2bd6d21ae0 |
completed | March 22, 2026, 7:01 p.m. |
| PD | Predicate disambiguation | batch_69c0334412388190bc594794ec5754f9 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:55 p.m.