Triple
T26595355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Qarin |
E667474
|
entity |
| Predicate | ArabicRoot |
P33904
|
FINISHED |
| Object | q-r-n (to combine, join) |
—
|
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: q-r-n (to combine, join) | Statement: [Qarin, ArabicRoot, q-r-n (to combine, join)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ArabicRoot Context triple: [Qarin, ArabicRoot, q-r-n (to combine, join)]
-
A.
meaningInArabicRelatedForm
Indicates that one entity expresses the meaning of another entity in Arabic through a related or derived linguistic form.
-
B.
hasRootWord
chosen
Indicates that one linguistic form is derived from, based on, or directly associated with a specified root word.
-
C.
cognateInArabic
Indicates that a given term has a corresponding cognate form in Arabic that is historically or linguistically related in origin or structure.
-
D.
hasGivenNameFormInArabic
Indicates that an entity has a specific given-name form expressed in the Arabic language.
-
E.
verseTextArabic
Indicates the Arabic-language text content associated with a specific verse in a scriptural or poetic work.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61528e2b88190a35896a563572146 |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:10 a.m.