Triple
T34048502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barwar |
E873150
|
entity |
| Predicate | hasDialectNamedAfter |
P115576
|
FINISHED |
| Object | Barwar dialect of Neo-Aramaic |
—
|
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: Barwar dialect of Neo-Aramaic | Statement: [Barwar, hasDialectNamedAfter, Barwar dialect of Neo-Aramaic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDialectNamedAfter Context triple: [Barwar, hasDialectNamedAfter, Barwar dialect of Neo-Aramaic]
-
A.
hasDialectName
chosen
Indicates that a language, dialect, or linguistic variety is associated with a specific dialectal name or label.
-
B.
hasDialectCounterpart
Indicates that one linguistic form or expression has a corresponding equivalent in another dialect.
-
C.
haveDialect
Indicates that an entity uses, speaks, or is associated with a particular dialect or regional linguistic variety.
-
D.
hasDialectsIn
Indicates that a language or linguistic variety possesses distinct dialects that are used or found within a specified region or context.
-
E.
hasDialects
Indicates that an entity (typically a language) possesses one or more distinct dialectal varieties.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: May 1, 2026, 1:51 a.m.