Triple
T19378109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lancaster palatine courts |
E484724
|
entity |
| Predicate | exercisedPowersOf |
P6502
|
FINISHED |
| Object | royal 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: royal courts | Statement: [Lancaster palatine courts, exercisedPowersOf, royal courts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exercisedPowersOf Context triple: [Lancaster palatine courts, exercisedPowersOf, royal courts]
-
A.
exercisedPowerFrom
Indicates that one entity exerted authority, control, or influence originating from a particular source, position, or location over another entity or context.
-
B.
exercisedPowerWith
Indicates that one entity actively used or exerted power in conjunction with another entity, implying a shared or coordinated exercise of authority or influence.
-
C.
exercisedPowerOver
chosen
Indicates that one entity exerted control, influence, or authority over another entity.
-
D.
exerciseOfPower
Indicates the exertion or application of authority, control, or influence by one entity over another or within a given context.
-
E.
typeOfPowerExercised
Indicates the specific kind or nature of power or authority that is being exercised in a given relationship or context.
- 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_69d8e8d460d88190abf0591c5c9d2b0c |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e61a5dc3048190830b55c8ca02e624 |
completed | April 20, 2026, 12:21 p.m. |
| PD | Predicate disambiguation | batch_69e4fd54f8e48190956e73dd8969164a |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:35 p.m.