Triple
T29844130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moldavian ASSR |
E757882
|
entity |
| Predicate | usedScriptForRomanian |
P150428
|
FINISHED |
| Object | Cyrillic script |
—
|
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: Cyrillic script | Statement: [Moldavian ASSR, usedScriptForRomanian, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedScriptForRomanian Context triple: [Moldavian ASSR, usedScriptForRomanian, Cyrillic script]
-
A.
usesScriptFor
chosen
Indicates that one entity employs or relies on a particular script or writing system for its representation, communication, or operation.
-
B.
nameInRomanian
Indicates that one entity is the Romanian-language name or designation of another entity.
-
C.
exampleRomanization
Indicates that one entity is a romanized representation (in Latin script) of the other entity’s original text or name.
-
D.
nativeNameScript
Indicates the writing system or script in which an entity’s native name is expressed.
-
E.
languageOfScriptPromoted
Indicates that a particular language is associated with and promoted through the use of a given writing script.
- 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_69f224593f6c81908785a560fe659f58 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6760bfa788190ad868de214807eba |
completed | May 2, 2026, 10:09 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:41 p.m.