Triple
T35536550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavia |
E1026944
|
entity |
| Predicate | transitionOfChanceryLanguageTo |
P183214
|
FINISHED |
| Object | Romanian |
—
|
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: Romanian | Statement: [Moldavia, transitionOfChanceryLanguageTo, Romanian]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transitionOfChanceryLanguageTo Context triple: [Moldavia, transitionOfChanceryLanguageTo, Romanian]
-
A.
usedLanguageInChancery
Indicates that a particular language was employed as the official medium of writing and record-keeping in a chancery or administrative office.
-
B.
usedLanguageAlongsideChancerySlavonic
chosen
Indicates that an additional language was used together with Chancery Slavonic in the same context or activity.
-
C.
hasChancery
Indicates that an entity possesses or is associated with a chancery, i.e., an official office or administrative body responsible for formal documents and records.
-
D.
historicalLanguageStage
Indicates that one language variety represents an earlier historical stage or developmental phase of another language.
-
E.
historicalLanguageFeature
Indicates that a language possesses a feature, trait, or characteristic that existed or was relevant in a past historical period.
- 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_69f76dff7e508190b28ceeee770dce23 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69ff56ef0a5c8190ae729d66a8cf7fc4 |
completed | May 9, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ff539859c481909ec56310da418688 |
completed | May 9, 2026, 3:32 p.m. |
Created at: May 3, 2026, 4:04 p.m.