Triple
T8192504
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Keeper of the Great Seal |
E191344
|
entity |
| Predicate | usedSealFor |
P10498
|
FINISHED |
| Object | formalizing acts of state |
—
|
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: formalizing acts of state | Statement: [Lord Keeper of the Great Seal, usedSealFor, formalizing acts of state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedSealFor Context triple: [Lord Keeper of the Great Seal, usedSealFor, formalizing acts of state]
-
A.
usedSeal
chosen
Indicates that an entity has applied or employed a seal (e.g., for closure, authentication, or protection) on another entity.
-
B.
usesSealImage
Indicates that one entity employs or incorporates the seal image of another entity in some context or medium.
-
C.
isSealed
Indicates that an entity is closed off or secured so that nothing can enter, exit, or be altered.
-
D.
sealedBy
Indicates that one entity is closed, secured, or made airtight/watertight through the action or presence of another entity.
-
E.
inscriptionUsedWith
Indicates that a particular inscription is employed together with, or in association with, another object, tool, or context in which it is applied or interpreted.
- 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_69ca82c5b6948190a583c096fb0a6c71 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb5c1d7aa48190adbbce88b3bed1a3 |
completed | March 31, 2026, 5:31 a.m. |
| PD | Predicate disambiguation | batch_69cb36aac86081909b83636e352e0ced |
completed | March 31, 2026, 2:51 a.m. |
Created at: March 30, 2026, 5:42 p.m.