Triple
T32282863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penal Law (1917 Code of Canon Law) |
E824746
|
entity |
| Predicate | codificationEra |
P123517
|
FINISHED |
| Object | Pio-Benedictine Code era |
—
|
NE NERFINISHED |
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: Pio-Benedictine Code era | Statement: [Penal Law (1917 Code of Canon Law), codificationEra, Pio-Benedictine Code era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codificationEra Context triple: [Penal Law (1917 Code of Canon Law), codificationEra, Pio-Benedictine Code era]
-
A.
timeOfCodification
Indicates the specific point in time at which something (such as a rule, law, or concept) was formally codified or recorded.
-
B.
timePeriodOfCodification
chosen
Indicates the time period during which something was formally codified or set into an official, systematic form.
-
C.
dateEnactedEraName
Indicates that a law, policy, or formal act was enacted during a specific named historical era.
-
D.
codificationLevel
Indicates the degree or extent to which something is formally systematized, standardized, or encoded into an explicit set of rules or structures.
-
E.
codificationEvent
Indicates an event in which rules, principles, or information are formally organized and recorded into a structured, codified 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_69f3490f404081908450db66884f4334 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bccc5be081908b121f4035b42dd9 |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6b632cf788190a3d0c08cd026b84b |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:43 a.m.