Triple
T16433115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord Clerk Register |
E399115
|
entity |
| Predicate | scopeOfRecords |
P53210
|
FINISHED |
| Object | public records of Scotland |
—
|
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: public records of Scotland | Statement: [Lord Clerk Register, scopeOfRecords, public records of Scotland]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfRecords Context triple: [Lord Clerk Register, scopeOfRecords, public records of Scotland]
-
A.
scopeOfControl
Indicates the extent or range within which an entity has authority, influence, or control over another entity or set of entities.
-
B.
scopeType
Indicates the specific range, level, or context within which a given relationship, rule, or action is defined or applies.
-
C.
archivesScope
chosen
Indicates that one entity defines or delimits the scope or coverage of another entity’s archival content or records.
-
D.
scopeOfReference
Indicates the range or domain of things, concepts, or entities to which a reference, statement, or expression applies.
-
E.
acquisitionScope
Indicates the extent, boundaries, or coverage of what is obtained or brought under control through an acquisition.
- 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_69d87f2b9024819085c20e52de95d583 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e32b9f2e8c81909c60b8fb78255e5f |
completed | April 18, 2026, 6:58 a.m. |
| PD | Predicate disambiguation | batch_69e22701d2288190bf8676050758f172 |
completed | April 17, 2026, 12:26 p.m. |
Created at: April 10, 2026, 5:10 a.m.