Triple
T22026231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian courts |
E543968
|
entity |
| Predicate | hadJudgeType |
P10518
|
FINISHED |
| Object | professional judges |
—
|
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: professional judges | Statement: [Prussian courts, hadJudgeType, professional judges]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadJudgeType Context triple: [Prussian courts, hadJudgeType, professional judges]
-
A.
hasJudge
Indicates that a legal case, proceeding, or decision is presided over or decided by a particular judge.
-
B.
hasJudgeType
chosen
Indicates that an entity is associated with a specific category or type of judge.
-
C.
hasJudges
Indicates that one entity serves as a judge or panel of judges for another entity, such as an event, competition, or legal case.
-
D.
hasPrincipalJudge
Indicates that one entity serves as the main or presiding judge for another entity, such as a court or judicial body.
-
E.
hasJuryType
Indicates that an entity is associated with, or classified by, a specific type or category of jury.
- 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_69e11e2e8ea4819084210fe06d3a1b8d |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cba61c8190a48ec2c1ee1315b0 |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.