Triple
T33791740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حزب وطني |
E865949
|
entity |
| Predicate | ينشط_في |
P129177
|
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.
alsoActiveIn
Indicates that an entity which is active in one context, domain, or location is additionally active in another specified context, domain, or location.
-
B.
involvedInWork
Indicates that an entity participates in, contributes to, or is otherwise engaged in a particular work, project, or activity.
-
C.
traditionallyInvolvedIn
Indicates that an entity has historically or customarily participated in, practiced, or been associated with a particular activity, role, or domain.
-
D.
activityType
Indicates the specific kind or category of action or event that an entity is engaged in or associated with.
-
E.
notableActivityIn
chosen
Indicates that an entity is particularly recognized for performing a significant activity within a specified place, context, or domain.
- 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.