Triple
T5040260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supreme Court of Judicature at Fort William |
E113525
|
entity |
| Predicate | hadNumberOfJudges |
P2279
|
FINISHED |
| Object | 4 |
—
|
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 | Statement: [Supreme Court of Judicature at Fort William, hadNumberOfJudges, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNumberOfJudges Context triple: [Supreme Court of Judicature at Fort William, hadNumberOfJudges, 4]
-
A.
numberOfJudges
chosen
Indicates the total count of judges associated with a particular case, event, or entity.
-
B.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
C.
hasNumberOfJurors
Indicates the relationship specifying how many jurors are associated with a given legal case, trial, or proceeding.
-
D.
hasJurors
Indicates that one entity serves as or includes jurors in relation to another entity, typically in the context of a legal case or proceeding.
-
E.
hasSubJuries
Indicates that an entity (typically a main jury or committee) is composed of or associated with one or more subordinate juries.
- 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_69bd44384298819089c49e7c330ec7b8 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd73dd27fc8190817e53311ea3f706 |
completed | March 20, 2026, 4:20 p.m. |
| PD | Predicate disambiguation | batch_69bd71529d608190a53470ba6c14bb1d |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:37 p.m.