Triple
T1653767
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | African National Congress |
E35751
|
entity |
| Predicate | adoptedFreedomCharter |
P29035
|
FINISHED |
| Object | 1955 |
—
|
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: 1955 | Statement: [African National Congress, adoptedFreedomCharter, 1955]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedFreedomCharter Context triple: [African National Congress, adoptedFreedomCharter, 1955]
-
A.
charterAdoptedIn
chosen
Indicates that a charter was formally adopted or enacted at a specific time or in a specific place.
-
B.
grantedCharter
Indicates that an authority formally issued an official charter or authorization to an entity.
-
C.
foundingResolution
Indicates that an entity serves as the formal founding resolution or charter that establishes or initiates another entity (such as an organization, project, or institution).
-
D.
constitutionAdopted
Indicates that a particular constitution has been formally accepted and put into effect by the relevant authority or polity.
-
E.
introducedLegalCharter
Indicates that an entity formally established or brought into effect a legal charter governing another entity 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_69a8860568888190a32cd9f70acbba42 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69a907cff53c8190b424f088478d3e2c |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:29 p.m.