Triple
T1145092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book 7A |
E23545
|
entity |
| Predicate | legalCodeType |
P24436
|
FINISHED |
| Object | codified statute |
—
|
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: codified statute | Statement: [Book 7A, legalCodeType, codified statute]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legalCodeType Context triple: [Book 7A, legalCodeType, codified statute]
-
A.
legalCodeRecordedIn
Indicates that a legal code is documented, registered, or officially stored within a particular record, system, or repository.
-
B.
legalCitationType
Indicates the specific kind or category of legal citation that characterizes the relationship between the citing and cited legal sources.
-
C.
typeOfLaw
Indicates that one entity is a specific category or kind of law to which the other entity pertains.
-
D.
legalAuthorityType
Indicates the specific kind or category of legal authority that governs, authorizes, or regulates an entity or action.
-
E.
notableLegalCode
Indicates that a legal code is especially significant, influential, or noteworthy in relation to the referenced 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_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. |
| PDg | Predicate description generation | batch_69a4bbb9fb4c81909dd39c496893c21b |
completed | March 1, 2026, 10:20 p.m. |
Created at: March 1, 2026, 7:44 p.m.