Triple
T36624092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | كتاب الحدود |
E904123
|
entity |
| Predicate | يُصنَّفضمن |
P186094
|
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.
favored
Indicates that one entity is preferred, supported, or given advantage over others by another entity.
-
B.
favoredFor
Indicates that something is preferred or commonly chosen for a particular purpose, use, or context.
-
C.
disfavoured
Indicates that one entity holds a negative, unfavorable, or less preferred attitude or treatment toward another entity compared to alternatives.
-
D.
endoPreference
Indicates a preference or tendency for something to occur or be located within the interior or internal part of an entity.
-
E.
contrastsPreferenceFor
Indicates a relationship where one entity’s preference is compared against and shown to differ from another entity’s preference.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c83f5960819089610ed39c839678 |
completed | May 3, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
| PDg | Predicate description generation | batch_69f7c776b4088190bef550c869da530d |
completed | May 3, 2026, 10:08 p.m. |
Created at: May 3, 2026, 4:11 p.m.