Triple
T4077692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. states |
E87403
|
entity |
| Predicate | haveCivilLaw |
P52876
|
FINISHED |
| Object | state civil 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: state civil code | Statement: [U.S. states, haveCivilLaw, state civil code]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: haveCivilLaw Context triple: [U.S. states, haveCivilLaw, state civil code]
-
A.
legalSystem
Indicates the formal framework of laws, rules, and institutions that governs how legal matters are defined, interpreted, and enforced within a society or jurisdiction.
-
B.
hasCivilSection
Indicates that one legal document, case, or record includes or is associated with a specific civil law section or provision.
-
C.
legalDoctrine
Indicates that one legal principle, rule, or theory is being applied, referenced, or relied upon as an authoritative basis for interpreting or deciding a legal issue.
-
D.
branchOfLaw
Indicates a relationship where one legal field or discipline is a subdivision or specialized area within a broader body of law.
-
E.
relatedLegalSystem
Indicates that there is an association or connection between two legal systems, such as influence, similarity, shared origin, or mutual relevance.
- 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_69aed9435cf48190ad1da737c962d19d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefc4d348c8190a94724639830aca0 |
completed | March 9, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69aef9082c2081908474f082a49bebc8 |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aef9b34dec81909bbc3def9decc71a |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:39 p.m.