Triple
T24733520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the King in Chancery |
E618351
|
entity |
| Predicate | decidedMatters |
P157212
|
FINISHED |
| Object | appeals from ecclesiastical courts |
—
|
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: appeals from ecclesiastical courts | Statement: [the King in Chancery, decidedMatters, appeals from ecclesiastical courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidedMatters Context triple: [the King in Chancery, decidedMatters, appeals from ecclesiastical courts]
-
A.
decidedMatters
chosen
Indicates that one entity has formally resolved, determined, or settled specific issues or questions concerning another entity.
-
B.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
C.
decisionsTakenBy
Indicates that one or more decisions are made or taken by a specified agent or entity.
-
D.
decisionsAre
Indicates that certain choices, judgments, or resolutions possess a specified quality, status, or classification.
-
E.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
- 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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442a977b08190b44eac040cb90211 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 4:03 a.m.