Triple
T5288943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Danish Code of 1683 |
E119692
|
entity |
| Predicate | codificationType |
P2202
|
FINISHED |
| Object | comprehensive code |
—
|
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: comprehensive code | Statement: [Danish Code of 1683, codificationType, comprehensive code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codificationType Context triple: [Danish Code of 1683, codificationType, comprehensive code]
-
A.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
B.
codifiedIn
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
C.
codificationTopicNumber
Indicates the numbered topic or subject under which something is organized or classified in a codification system.
-
D.
legalCodeType
Indicates the specific category or classification of a legal code that applies to an entity or situation.
-
E.
codeType
chosen
Indicates the classification or category assigned to a particular code within a coding or encoding 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd8682d18c8190bbb35cc75c8a7c12 |
completed | March 20, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69bd844dfdac819086efedd1cbebff84 |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:52 p.m.