Triple
T4709802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great Seal of the Court of the Lord Lyon |
E104479
|
entity |
| Predicate | typeOfDocumentSealed |
P24327
|
FINISHED |
| Object | letters patent |
—
|
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: letters patent | Statement: [Great Seal of the Court of the Lord Lyon, typeOfDocumentSealed, letters patent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDocumentSealed Context triple: [Great Seal of the Court of the Lord Lyon, typeOfDocumentSealed, letters patent]
-
A.
sealType
Indicates the specific kind or category of seal associated with an entity or connection.
-
B.
documentTypeUsed
chosen
Indicates that a particular type or category of document is employed or applied in a given context or activity.
-
C.
signatoryType
Indicates the specific role or category of a party that has signed or formally agreed to a document, contract, or agreement.
-
D.
documentTypeIncluded
Indicates that a particular document type is contained within, or is part of, a specified set or collection of document types.
-
E.
documentationType
Indicates the specific category or kind of documentation associated with or required for an entity or process.
- 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_69bd43eac3c08190af7e4020c6c3704c |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd680beb508190b3d74e20e1c64405 |
completed | March 20, 2026, 3:30 p.m. |
| PD | Predicate disambiguation | batch_69bd621ddcd88190903288566f5e5dab |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:17 p.m.