Triple
T2051891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gagauz |
E45586
|
entity |
| Predicate | languageStatusInGagauzia |
P17042
|
FINISHED |
| Object | official language |
—
|
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: official language | Statement: [Gagauz, languageStatusInGagauzia, official language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageStatusInGagauzia Context triple: [Gagauz, languageStatusInGagauzia, official language]
-
A.
nationalLanguageStatus
chosen
Indicates that a language holds official or nationally recognized status within a country or political entity.
-
B.
languageOfOfficialAnnouncements
Indicates the language used for formal or official public announcements issued by an authority.
-
C.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
-
D.
languageFamilyStatus
Indicates the classification or recognition status of a language within a particular language family (e.g., primary, branch, extinct, or disputed).
-
E.
languageEndangermentStatus
Indicates the degree to which a language is at risk of falling out of use or becoming extinct.
- 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_69a8891948208190ab7898da21824c77 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb99078d88190bc30fa4596f0bae8 |
completed | March 7, 2026, 5:37 a.m. |
| PD | Predicate disambiguation | batch_69abb7abba508190b872f345d3ba51bb |
completed | March 7, 2026, 5:29 a.m. |
Created at: March 4, 2026, 7:39 p.m.