Triple
T33791765
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | حزب وطني |
E865949
|
entity |
| Predicate | يخضع_ل |
P1313
|
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.
unterliegt
Indicates that one entity is subject to, governed or constrained by the authority, rules, influence, or control of another entity.
-
B.
holdsUnder
Indicates that one entity maintains possession, control, or validity of another entity subject to certain conditions, constraints, or a specific context.
-
C.
indicatesSubjugation
Indicates that one entity is under the domination, control, or authority of another, reflecting a hierarchical power imbalance or enforced obedience.
-
D.
isSubjectTo
chosen
Indicates that one entity is governed, affected, or constrained by the authority, rules, conditions, or influence of another entity.
-
E.
under
Indicates that one entity is positioned below or beneath another entity, often implying vertical alignment or coverage.
- 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.