Triple
T24733507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the King in Chancery |
E618351
|
entity |
| Predicate | replacedAppealTo |
P157824
|
FINISHED |
| Object | external 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: external courts | Statement: [the King in Chancery, replacedAppealTo, external courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: replacedAppealTo Context triple: [the King in Chancery, replacedAppealTo, external courts]
-
A.
hasAppealsTo
Indicates that one entity formally challenges or seeks review of a decision, judgment, or outcome through another entity or process.
-
B.
replacedBecause
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
C.
appealsFor
Indicates that one entity formally requests support, intervention, or a favorable decision from another entity.
-
D.
appealBeyond
Indicates that something has significance, relevance, or attractiveness that extends beyond a specified scope, group, or context.
-
E.
centralAppeal
Indicates that something serves as the main attraction, focus, or compelling feature that draws interest or attention.
- F. None of above. chosen
Provenance (4 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_69f453035f508190be83a3d521723acf |
completed | May 1, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69f44d6ef33081908f5d36ba1ae5f473 |
completed | May 1, 2026, 6:51 a.m. |
| PDg | Predicate description generation | batch_69f45300bd488190bb1d4160f5534ef6 |
completed | May 1, 2026, 7:15 a.m. |
Created at: April 18, 2026, 4:03 a.m.