Triple
T28022651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | There Shall Be Peace and Friendship! |
E707729
|
entity |
| Predicate | documentSectionOf |
P3120
|
FINISHED |
| Object | South African 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: South African Freedom Charter | Statement: [There Shall Be Peace and Friendship!, documentSectionOf, South African Freedom Charter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: documentSectionOf Context triple: [There Shall Be Peace and Friendship!, documentSectionOf, South African Freedom Charter]
-
A.
councilDocumentSectionOf
Indicates that one document section belongs to, or forms a part of, a specific council document.
-
B.
documentationSection
Indicates that one entity is a specific section or subdivision within the documentation of another entity.
-
C.
section
chosen
Indicates that one entity is a distinct part, division, or segment of another entity within a larger whole.
-
D.
sectionProvided
Indicates that a specific section or portion of content has been supplied or made available by one entity to another.
-
E.
isSectionOfDocumentType
Indicates that one entity is a section or component belonging to a specific type of document.
- 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_69ef96baf3a881909a2b63844185dddd |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69f66c5c13808190887180099745673b |
completed | May 2, 2026, 9:27 p.m. |
| PD | Predicate disambiguation | batch_69f66abddc448190a488852f8abdeb2c |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 27, 2026, 8:11 p.m.