Triple
T36001732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | العرش |
E1041149
|
entity |
| Predicate | يُنسب_إليه |
P181941
|
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.
notablyAssociatedWith
Indicates that one entity is prominently or distinctively connected with another in a way that is especially noteworthy or remarkable.
-
B.
повʼязанеЗ
Indicates a general association or connection between one entity and another.
-
C.
ייחוס
Indicates an attribution or assignment relationship, where a property, role, or characteristic is ascribed from one entity to another.
-
D.
isAssociatedWith
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
E.
atribuidoA
chosen
Indicates that something (such as a work, action, or characteristic) is assigned or credited to a particular entity as its source or author.
- 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.