Triple
T22526844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | دعاء الكروان |
E556926
|
entity |
| Predicate | يُعد من |
P133983
|
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.
memberFrom
chosen
Indicates that an entity is a member originating from, or associated with, a particular source, group, or location.
-
B.
hasRoleInFormationOf
Indicates that an entity plays a specific role or function in the creation, development, or establishment of another entity or structure.
-
C.
isSuitableFor
Indicates that one entity is appropriate, fitting, or well-matched for use, application, or association with another entity.
-
D.
considersItself
Indicates that an entity regards or perceives itself in a particular way, role, or state.
-
E.
considered
Indicates that one entity regards, judges, or thinks about another entity in a particular way or context.
- 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_69e11e57483c8190b0887c4f8ff26446 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ed411488190a51320930b9805c2 |
completed | April 29, 2026, 1:28 a.m. |
| PD | Predicate disambiguation | batch_69ee625e3b408190a60c759fb0b28fe2 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 16, 2026, 8:51 p.m.