Triple
T21141041
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1824 Saint Petersburg flood |
E520925
|
entity |
| Predicate | languageOfPrimaryHistoricalAccounts |
P30358
|
FINISHED |
| Object | Russian |
—
|
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: Russian | Statement: [1824 Saint Petersburg flood, languageOfPrimaryHistoricalAccounts, Russian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfPrimaryHistoricalAccounts Context triple: [1824 Saint Petersburg flood, languageOfPrimaryHistoricalAccounts, Russian]
-
A.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
B.
languageOfHistoricalActivity
Indicates the language in which a historical activity, event, or action was conducted or recorded.
-
C.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
D.
historicalLanguage
Indicates that one language is a historical or earlier form/ancestor of another language.
-
E.
languageOfHistoricName
Indicates the language in which a historic or former name of an entity is expressed.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7235f77708190809d6aa3ee8056aa |
completed | April 21, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69e5f5ed6c8c8190b31092a5d4c3de5d |
completed | April 20, 2026, 9:46 a.m. |
Created at: April 16, 2026, 2:57 p.m.