Triple
T34199331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treason Trial (South Africa) |
E877329
|
entity |
| Predicate | evidenceIncluded |
P140693
|
FINISHED |
| Object | Freedom Charter |
—
|
NE NERFINISHED |
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: Freedom Charter | Statement: [Treason Trial (South Africa), evidenceIncluded, Freedom Charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: evidenceIncluded Context triple: [Treason Trial (South Africa), evidenceIncluded, Freedom Charter]
-
A.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
B.
evidenceCited
chosen
Indicates that one entity is used as supporting evidence or citation for the claims or content of another entity.
-
C.
hasEvidenceItem
Indicates that there exists a specific piece of evidence supporting, illustrating, or justifying the associated entity or claim.
-
D.
evidenceAtIssue
Indicates that a particular piece of evidence is directly contested, disputed, or central to the disagreement or decision in a case or situation.
-
E.
evidenceHandling
Indicates how evidence is collected, processed, stored, and transferred within an investigation or legal 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f7102ae9788190b72c042d09e75cf8 |
completed | May 3, 2026, 9:06 a.m. |
| PD | Predicate disambiguation | batch_69f70f3c5bfc81908585f52e196dafe5 |
completed | May 3, 2026, 9:02 a.m. |
Created at: May 1, 2026, 1:55 a.m.