Triple
T22438537
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasine Register |
E554691
|
entity |
| Predicate | basisOfRegistration |
P7051
|
FINISHED |
| Object | recorded deeds |
—
|
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: recorded deeds | Statement: [Sasine Register, basisOfRegistration, recorded deeds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basisOfRegistration Context triple: [Sasine Register, basisOfRegistration, recorded deeds]
-
A.
basisOfOrganization
Indicates that one entity serves as the foundational principle, criterion, or structure upon which another entity is organized or arranged.
-
B.
officialRegisterOf
Indicates that one entity serves as the authoritative, formally maintained record or registry for another entity.
-
C.
basisOfOffice
Indicates the foundational principle, authority, or justification upon which an office or official position is established or exercised.
-
D.
usedAsBasisFor
chosen
Indicates that one entity serves as the foundation, reference, or starting point upon which another entity is developed, derived, justified, or constructed.
-
E.
certificationBasis
Indicates the standard, criteria, or authority on which a certification or official approval is founded.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae01bd08190aee5141f4c0848bc |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.