Triple
T15814315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zakonopravilo |
E383434
|
entity |
| Predicate | secularFunction |
P22742
|
FINISHED |
| Object | codification of civil law |
—
|
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: codification of civil law | Statement: [Zakonopravilo, secularFunction, codification of civil law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secularFunction Context triple: [Zakonopravilo, secularFunction, codification of civil law]
-
A.
hasSecularAspects
Indicates that something includes or exhibits non-religious, worldly, or secular characteristics or dimensions.
-
B.
cosmologicalFunction
Indicates the role or effect an entity has within a cosmological system or framework, such as how it contributes to the structure, behavior, or evolution of the universe.
-
C.
extremalFunction
Indicates that a function attains an extreme value (such as a minimum or maximum) under given conditions or over a specified domain.
-
D.
hasSecularUse
chosen
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
E.
traditionalFunction
Indicates that an entity serves a customary or historically established role or purpose within a cultural or social context.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a1571881909488728f123865ad |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.