Triple
T33791764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حزب وطني |
E865949
|
entity |
| Predicate | يعمل_ضمن |
P144725
|
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.
workWithin
chosen
Indicates that one entity performs its activities or duties inside the boundaries, scope, or context defined by another entity.
-
B.
works in
Indicates that one entity performs their job or professional activities within the organization, location, or context represented by another entity.
-
C.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by another entity.
-
D.
workWith
Indicates that one entity collaborates or engages in work-related activities together with another entity.
-
E.
mayWorkIn
Indicates that an entity is allowed or has the possibility to work in a particular place, organization, 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:45 a.m.