Triple
T1085065
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Egyptian Arabic |
E24030
|
entity |
| Predicate | statusInEgypt |
P24057
|
FINISHED |
| Object | de facto national spoken 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: de facto national spoken language | Statement: [Egyptian Arabic, statusInEgypt, de facto national spoken language]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInEgypt Context triple: [Egyptian Arabic, statusInEgypt, de facto national spoken language]
-
A.
statusInIran
Indicates the legal, social, or political standing or condition of an entity specifically within the context of Iran.
-
B.
statusInRussia
Indicates the legal, social, or operational condition or standing that something or someone has specifically within the context of Russia.
-
C.
statusInAfghanistan
Indicates the condition, role, or legal standing an entity holds within the context of Afghanistan.
-
D.
statusInPakistan
Indicates the legal, social, or operational condition or standing that something or someone has within the context of Pakistan.
-
E.
status
Indicates the current condition, state, or standing of an entity within a given context.
- F. None of above. chosen
Provenance (4 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b961d0cc8190858296b44fab2f32 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.