Triple
T2316559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charter Act 1833 |
E51077
|
entity |
| Predicate | increasedNumberOfCouncilMembersTo |
P38036
|
FINISHED |
| Object | 4 ordinary members |
—
|
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: 4 ordinary members | Statement: [Charter Act 1833, increasedNumberOfCouncilMembersTo, 4 ordinary members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: increasedNumberOfCouncilMembersTo Context triple: [Charter Act 1833, increasedNumberOfCouncilMembersTo, 4 ordinary members]
-
A.
increasedNumberOfElectors
Indicates that the number of electors associated with an entity has grown compared to a previous state or reference point.
-
B.
hasNumberOfCouncillors
Indicates the relationship that specifies how many councillors are associated with a given entity.
-
C.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
-
D.
numberOfElectedMembers
Indicates the total count of individuals who have been formally chosen through an election to serve as members of a given body or group.
-
E.
numberOfCommitteeMembers
Indicates the total count of individuals who are members of a given committee.
- 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.