Triple
T2316560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Act 1833 |
E51077
|
entity |
| Predicate | createdPost |
P38037
|
FINISHED |
| Object | Law Member in Governor-General’s Council |
—
|
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: Law Member in Governor-General’s Council | Statement: [Charter Act 1833, createdPost, Law Member in Governor-General’s Council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdPost Context triple: [Charter Act 1833, createdPost, Law Member in Governor-General’s Council]
-
A.
createdStatus
Indicates that an entity has been newly created and is in its initial or just-established state within a system or process.
-
B.
createdBody
Indicates that one entity brought another entity into existence or produced it as a result of its actions.
-
C.
createdProgram
Indicates that an entity authored, developed, or produced a particular program (such as software or a coded application).
-
D.
createdAfterEvent
Indicates that the creation of one entity occurred after a specified event in time.
-
E.
createdTo
Indicates that one entity was brought into existence, produced, or designed specifically for the purpose, use, or function of another entity.
- F. None of above. chosen
Provenance (4 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_69a88b074b908190ae983dbca7757d88 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abc685f05481909c863b29d1f6bacd |
completed | March 7, 2026, 6:32 a.m. |
| PD | Predicate disambiguation | batch_69abc58e88e481908733fdf79d3f8a15 |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abc682d094819081a96ffb77c4c42a |
completed | March 7, 2026, 6:32 a.m. |
Created at: March 4, 2026, 7:49 p.m.