Triple
T25456756
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | صاحب رفادة الحاج |
E637933
|
entity |
| Predicate | يتطلب |
P100
|
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.
requires
chosen
Indicates that one entity must exist, occur, or be satisfied before another entity can exist, occur, or be carried out.
-
B.
requiredTo
Indicates that one entity has an obligation or necessity to perform an action or satisfy a condition in relation to another entity or context.
-
C.
requiredBy
Indicates that one entity depends on or cannot function properly without another entity being present, completed, or satisfied.
-
D.
requiresInitiationIn
Indicates that one entity must be initiated, started, or activated within the context, scope, or environment defined by another entity.
-
E.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
- 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_69e75db8bab08190baca80b4a8c315fd |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f72756748190aa315cc00882a798 |
completed | May 2, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:10 p.m.