Triple
T717632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earl of Chester |
E14343
|
entity |
| Predicate | governancePowers |
P7884
|
FINISHED |
| Object | quasi-regal authority in Cheshire |
—
|
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: quasi-regal authority in Cheshire | Statement: [Earl of Chester, governancePowers, quasi-regal authority in Cheshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governancePowers Context triple: [Earl of Chester, governancePowers, quasi-regal authority in Cheshire]
-
A.
governance
Indicates the relationship in which one entity exercises authority, control, or decision-making power over the policies, actions, or direction of another entity or system.
-
B.
governanceModel
Indicates the type or structure of authority, decision-making, and control that defines how an entity is directed and overseen.
-
C.
governanceArea
Indicates the geographic or jurisdictional area over which an entity has governing authority or responsibility.
-
D.
grantedPower
chosen
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
E.
governs
Indicates that one entity exercises authoritative control, direction, or rule over another entity or domain.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a577658881909c12951d63d96377 |
completed | March 1, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f38898819089d79bad4f4ff2d2 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:37 p.m.