Triple
T8660227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Lieutenant of Northamptonshire |
E205528
|
entity |
| Predicate | changedFunction |
P6654
|
FINISHED |
| Object | now primarily ceremonial |
—
|
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: now primarily ceremonial | Statement: [Lord Lieutenant of Northamptonshire, changedFunction, now primarily ceremonial]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedFunction Context triple: [Lord Lieutenant of Northamptonshire, changedFunction, now primarily ceremonial]
-
A.
functionChange
chosen
Indicates that an entity’s function, role, or operational behavior has been altered from one state or purpose to another.
-
B.
changedFrom
Indicates that an entity previously had one state, value, or form and was altered or updated from that prior condition to a new one.
-
C.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
-
D.
formerFunction
Indicates that an entity previously held a specific role, position, or function but no longer does so.
-
E.
changesProperty
Indicates that one entity causes a change in a specific property or attribute of 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_69ca8350897c819086cde7596fbe5fe7 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc48701c748190a5f7bd9e2da0e5e9 |
completed | March 31, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69cc4564e018819081036722f3e42a71 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:30 p.m.