Triple
T6120740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwe Human Rights Commission |
E136475
|
entity |
| Predicate | canSueAndBeSued |
P1629
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Zimbabwe Human Rights Commission, canSueAndBeSued, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canSueAndBeSued Context triple: [Zimbabwe Human Rights Commission, canSueAndBeSued, yes]
-
A.
canBeSuedAs
Indicates that one entity has legal standing or capacity to be the target of a lawsuit initiated by another entity.
-
B.
canBeSuedFor
Indicates that one party is legally liable or potentially subject to legal action by another party for a specified cause or wrongdoing.
-
C.
legalSubject
chosen
Indicates that an entity is the bearer of legal rights, duties, or responsibilities within a legal relationship or context.
-
D.
legalOrigin
Indicates the foundational legal system or jurisdiction from which an entity’s laws, regulations, or legal framework are derived.
-
E.
supportsJurisdiction
Indicates that one jurisdiction provides backing, authority, or legal support for the actions, decisions, or existence of another jurisdiction.
- 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_69c0089f851c81909e5e189a617dcff6 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bef8dc08190b917ad7209188c62 |
completed | March 22, 2026, 9:15 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:14 p.m.