Triple
T1145100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book 7A |
E23545
|
entity |
| Predicate | codification |
P775
|
FINISHED |
| Object | part of the Burgerlijk Wetboek |
—
|
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: part of the Burgerlijk Wetboek | Statement: [Book 7A, codification, part of the Burgerlijk Wetboek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codification Context triple: [Book 7A, codification, part of the Burgerlijk Wetboek]
-
A.
codifiedIn
chosen
Indicates that something is formally recorded, defined, or established within a specific document, code, or legal/institutional text.
-
B.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
C.
timeOfCodification
Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
-
D.
legislatedUnder
Indicates that a law, regulation, or policy was created, enacted, or established according to the authority, framework, or provisions of a specific higher-level law or legal regime.
-
E.
code
Indicates that an entity writes, develops, or produces computer software or source code.
- 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_69a493ef399c8190b04b9146d2314f59 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4bc51244c8190bcd533f3e80c8f17 |
completed | March 1, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69a4bb4d4104819084027a043c6118cb |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:44 p.m.