Triple
T26137963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ruqaʿa |
E659432
|
entity |
| Predicate | diacriticUsage |
P2270
|
FINISHED |
| Object | often omitted in everyday writing |
—
|
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: often omitted in everyday writing | Statement: [Ruqaʿa, diacriticUsage, often omitted in everyday writing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: diacriticUsage Context triple: [Ruqaʿa, diacriticUsage, often omitted in everyday writing]
-
A.
diacriticFunction
Indicates that a diacritic serves a particular role or effect in relation to the base character or linguistic unit it modifies.
-
B.
diacriticType
Indicates the specific kind or category of diacritic mark associated with a character or symbol.
-
C.
usesDiacritics
chosen
Indicates that the referenced text or linguistic element employs diacritical marks as part of its written form.
-
D.
usesDiacriticsFrom
Indicates that one entity employs or incorporates the diacritical marks that originate from or are characteristic of another entity.
-
E.
diacriticForms
Indicates that one written form is a diacritic variant or includes diacritic marks relative to another form.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be1d2408190820365bf7d8436bd |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5b0021da88190bdd4cf2698c23edf |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:18 p.m.