Triple
T3619972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yafiʿi Arabic |
E76698
|
entity |
| Predicate | linguisticLevel |
P10465
|
FINISHED |
| Object | dialect |
—
|
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: dialect | Statement: [Yafiʿi Arabic, linguisticLevel, dialect]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: linguisticLevel Context triple: [Yafiʿi Arabic, linguisticLevel, dialect]
-
A.
languageCapacity
Indicates the extent to which an entity is able to understand, produce, or otherwise use language.
-
B.
linguisticType
Indicates the type or category of language or linguistic system associated with an entity (e.g., spoken, signed, written, or other linguistic modality).
-
C.
linguisticFeature
Indicates a relationship where a linguistic property, pattern, or characteristic is attributed to or associated with a language-related entity (such as a word, phrase, or text).
-
D.
linguisticClassification
chosen
Indicates the relationship by which an entity is categorized according to its language or linguistic type.
-
E.
languageOfExpression
Indicates that a particular language is used as the medium or form in which an expression (such as a text, utterance, or work) is realized.
- 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_69ad85dae2fc81908d1ceadbc6af0089 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc2b85f6c819091000e231d9dac87 |
completed | March 8, 2026, 6:40 p.m. |
| PD | Predicate disambiguation | batch_69adb83f1e4c8190ab501c1c05b14c08 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:23 p.m.