Triple
T33791736
| 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.
administeredWithinFrameworkOf
Indicates that an action or process is carried out under, and in accordance with, a specified framework, system, or governing structure.
-
D.
workFor
Indicates that one entity is employed by or performs work under the authority or direction of another entity.
-
E.
operatesWithin
Indicates that one entity carries out its activities, functions, or operations inside the scope, boundaries, or jurisdiction defined by 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:45 a.m.