Triple
T24720399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | الراغب الأصفهاني |
E612276
|
entity |
| Predicate | اهتمام_خاص |
P66206
|
FINISHED |
| Object | بيان الفروق الدقيقة بين الألفاظ المتقاربة المعنى |
—
|
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: بيان الفروق الدقيقة بين الألفاظ المتقاربة المعنى | Statement: [الراغب الأصفهاني, اهتمام_خاص, بيان الفروق الدقيقة بين الألفاظ المتقاربة المعنى]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: اهتمام_خاص Context triple: [الراغب الأصفهاني, اهتمام_خاص, بيان الفروق الدقيقة بين الألفاظ المتقاربة المعنى]
-
A.
subjectInterest
chosen
Indicates that the subject has an interest in, or is concerned with, the object.
-
B.
loveInterest
Indicates that one entity is the romantic object of affection or attraction for another entity.
-
C.
interestMayBe
Indicates that one entity potentially has an interest in, or may be interested in, another entity or subject.
-
D.
صلة
Indicates a general connection, relationship, or linkage between two or more entities.
-
E.
secondaryInterest
Indicates that an entity has a secondary, less primary but still relevant interest or focus in relation to another entity or topic.
- 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_69e2d7d6e7a48190bb43b0d8bb1137a0 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f410fe3b848190ae296a29f742ee30 |
completed | May 1, 2026, 2:33 a.m. |
| PD | Predicate disambiguation | batch_69f40ee8ada8819089a7016b50308ff0 |
completed | May 1, 2026, 2:24 a.m. |
Created at: April 18, 2026, 3:40 a.m.