Triple
T17027330
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bečej municipality |
E413099
|
entity |
| Predicate | usesOfficialScript |
P4434
|
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: [Bečej municipality, usesOfficialScript, Cyrillic script]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesOfficialScript Context triple: [Bečej municipality, usesOfficialScript, Cyrillic script]
-
A.
officialScriptOf
chosen
Indicates that one writing system is formally designated as the standard or legally recognized script used for a particular language, region, or entity.
-
B.
notOfficialScriptFor
Indicates that a given writing system is explicitly not recognized or used as the official script for a particular language or entity.
-
C.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
D.
isOfficial
Indicates that an entity holds formal, authorized, or government-recognized status in a given context.
-
E.
usedInScripts
Indicates that something (such as a tool, method, or resource) is employed or referenced within one or more scripts.
- 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_69d886cc4170819093deddc7b8b4b6a7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d5d5ed388190871aa738cac04b65 |
completed | April 18, 2026, 7:04 p.m. |
| PD | Predicate disambiguation | batch_69e35d5be7f48190af9db67a1e23850f |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.