Triple
T31840947
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shatrah District |
E812800
|
entity |
| Predicate | hasDeJureLanguage |
P45194
|
FINISHED |
| Object | Arabic |
—
|
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: Arabic | Statement: [Shatrah District, hasDeJureLanguage, Arabic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDeJureLanguage Context triple: [Shatrah District, hasDeJureLanguage, Arabic]
-
A.
hasRepresentativeLanguage
Indicates that an entity is associated with a language that serves as its primary or officially recognized means of representation or communication.
-
B.
hasLanguageInCountry
Indicates that a particular language is used or recognized within a specified country.
-
C.
hasNotableLanguageWithOfficialStatusIn
chosen
Indicates that a language holds an officially recognized and notable status within a specified jurisdiction or region.
-
D.
hasLanguageLegislation
Indicates that there exists formal legislation or legal provisions governing the use, status, or regulation of language in relation to the subject entity.
-
E.
hasLanguageStatus
Indicates that an entity has a particular status or condition regarding its language use, recognition, or classification.
- 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_69f348ea7ffc8190a2ab43d80277cf59 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe6fea4a288190bf8615c5d6bf41b4 |
completed | May 8, 2026, 11:21 p.m. |
| PD | Predicate disambiguation | batch_69fe6f774de08190975a2393b9a1fd22 |
completed | May 8, 2026, 11:19 p.m. |
Created at: April 30, 2026, 11:49 p.m.