Triple
T8203261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Badawi Najdi Arabic |
E191628
|
entity |
| Predicate | moreSimilarTo |
P81483
|
FINISHED |
| Object | other Bedouin Arabic dialects |
—
|
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: other Bedouin Arabic dialects | Statement: [Badawi Najdi Arabic, moreSimilarTo, other Bedouin Arabic dialects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: moreSimilarTo Context triple: [Badawi Najdi Arabic, moreSimilarTo, other Bedouin Arabic dialects]
-
A.
materiallySimilarTo
Indicates that two entities share substantially the same physical or material characteristics, composition, or properties, though they may not be exactly identical.
-
B.
hasSimilarAttraction
Indicates that two entities experience or exert a comparable level or type of attraction toward something or each other.
-
C.
similarDish
Indicates that two dishes share notable similarities, such as ingredients, preparation methods, flavor profile, or style.
-
D.
culturallySimilarTo
Indicates that two entities share comparable cultural characteristics, practices, or values.
-
E.
resembles
Indicates that one entity is similar in appearance, form, or characteristics to another.
- 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_69ca82c7f3e08190857bf1fc63b2a10c |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5df9cac08190a890ded4c7fbd393 |
completed | March 31, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_69cb36ad01ac81909609b15f6a6c8581 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb4ab5162c8190bddd696078689895 |
completed | March 31, 2026, 4:16 a.m. |
Created at: March 30, 2026, 5:43 p.m.