Triple
T16742031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Letters patent |
E406855
|
entity |
| Predicate | authenticatedBy |
P60443
|
FINISHED |
| Object | great seal |
—
|
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: great seal | Statement: [Letters patent, authenticatedBy, great seal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: authenticatedBy Context triple: [Letters patent, authenticatedBy, great seal]
-
A.
authorizedOn
Indicates that an entity has been granted official permission or rights to act, access, or operate on a specified object, resource, or context.
-
B.
usedToAuthorize
chosen
Indicates that something serves as the basis or instrument for granting permission, approval, or official power to perform an action.
-
C.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
-
D.
authorizedIn
Indicates that an entity has been granted official permission or legal authority to act, operate, or be valid within a specified context, domain, or jurisdiction.
-
E.
authenticationType
Indicates the method or mechanism used to verify and confirm an entity’s identity in an interaction or system.
- 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_69d8838ffb088190a0b11149929006bf |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e39c3f49808190b543d8da34031f3d |
completed | April 18, 2026, 2:59 p.m. |
| PD | Predicate disambiguation | batch_69e319c807788190901250ab6e0ca55f |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:21 a.m.