Triple
T22028543
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English ecclesiastical courts |
E544025
|
entity |
| Predicate | includedCourtType |
P8214
|
FINISHED |
| Object | consistory court |
—
|
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: consistory court | Statement: [English ecclesiastical courts, includedCourtType, consistory court]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedCourtType Context triple: [English ecclesiastical courts, includedCourtType, consistory court]
-
A.
hasTypeOfCourt
chosen
Indicates that an entity is associated with or classified by a specific type or category of court.
-
B.
superiorCourtsInclude
Indicates that certain superior courts encompass, contain, or have within their jurisdiction the specified subordinate courts or judicial bodies.
-
C.
hasCourts
Indicates that an entity possesses, contains, or is equipped with one or more courts (e.g., legal, sports, or judicial facilities).
-
D.
isPartOfCourtSystem
Indicates that one legal body, division, or component belongs to and operates within a larger court system.
-
E.
courtStyle
Indicates the manner or stylistic approach in which a court conducts its proceedings or presents its decisions.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127cdf5c08190ac804664d6e56fe2 |
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.