Triple
T28433216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coloured Persons Representative Council |
E715192
|
entity |
| Predicate | chamberFor |
P61483
|
FINISHED |
| Object | Coloured people |
—
|
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: Coloured people | Statement: [Coloured Persons Representative Council, chamberFor, Coloured people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberFor Context triple: [Coloured Persons Representative Council, chamberFor, Coloured people]
-
A.
chamberedFor
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
B.
forChamber
chosen
Indicates that something is intended for use in, associated with, or belonging to a particular chamber.
-
C.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
D.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
E.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
- 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_69efd6b253888190b3c7222ed6a403a8 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 1:41 a.m.