Triple
T185749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scots law |
E3975
|
entity |
| Predicate | codificationLevel |
P6692
|
FINISHED |
| Object | partially codified |
—
|
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: partially codified | Statement: [Scots law, codificationLevel, partially codified]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codificationLevel Context triple: [Scots law, codificationLevel, partially codified]
-
A.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
hasDivisionLevel
Indicates that one entity is associated with a specific hierarchical or organizational division level of another entity.
-
C.
hasLCClassification
Indicates that an entity is assigned a specific Library of Congress Classification code representing its subject or shelving category.
-
D.
deweyDecimalClassification
Indicates the Dewey Decimal System classification assigned to an item, expressing its subject-based placement within a library’s organizational scheme.
-
E.
securityClassification
Indicates the level or category of security sensitivity or access restriction assigned to an entity.
- F. None of above. chosen
Provenance (4 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_69a25497e2f08190a040f8c6e1842643 |
completed | Feb. 28, 2026, 2:36 a.m. |
| NER | Named-entity recognition | batch_69a2592867108190b5d316c055575449 |
completed | Feb. 28, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69a2566fb08c81908faff2fde552105d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a257e763d081908c54ad57d8d3060d |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:40 a.m.