Triple
T36002004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ذَا الْكِفْلِ |
E1041157
|
entity |
| Predicate | محل خلاف في |
P1406
|
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.
addressesConflictWithin
Indicates that one entity deals with, manages, or resolves a conflict that exists inside another entity or within its internal scope.
-
B.
conflictIn
chosen
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
-
C.
conflictLocation
Indicates the place or geographic area where a conflict, dispute, or confrontation occurs or is centered.
-
D.
relationshipConflictWith
Indicates a state of opposition, disagreement, or incompatibility between two entities within a relationship.
-
E.
holderConflict
Indicates a relationship where the current holder or possessor of something is in conflict or dispute over that holding, such as ownership, control, or rights.
- 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_69f76e2a02208190aedd1f9025a8b300 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7acaec1508190a38f2ac9cc5383e7 |
completed | May 3, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f7ab75387c819091afc3c2128eb903 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.