Triple
T19685579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | High Court of Justice for the trial of Charles I |
E472702
|
entity |
| Predicate | numberOfCommissionersSitting |
P21525
|
FINISHED |
| Object | about 68 |
—
|
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: about 68 | Statement: [High Court of Justice for the trial of Charles I, numberOfCommissionersSitting, about 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfCommissionersSitting Context triple: [High Court of Justice for the trial of Charles I, numberOfCommissionersSitting, about 68]
-
A.
numberOfCommissioners
chosen
Indicates the specific count of commissioners associated with a given entity or context.
-
B.
maximumNumberOfCommissioners
Indicates the upper limit on how many commissioners are allowed in a given governing body or context.
-
C.
numberOfResidentCommissioners
Indicates the quantity of resident commissioners associated with a given entity.
-
D.
numberOfCommitteeMembers
Indicates the total count of individuals who are members of a given committee.
-
E.
numberOfAppointedMembers
Indicates the specific count of members who have been formally appointed to a group, body, or position.
- 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e641c33b94819081bdeb56910f6ff8 |
completed | April 20, 2026, 3:09 p.m. |
| PD | Predicate disambiguation | batch_69e53039ea808190a9106a53f564ab92 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:45 p.m.