Triple
T18208252
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hurd v. Hodge |
E435960
|
entity |
| Predicate | enforcementMechanismAddressed |
P79850
|
FINISHED |
| Object | judicial enforcement of private covenants |
—
|
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: judicial enforcement of private covenants | Statement: [Hurd v. Hodge, enforcementMechanismAddressed, judicial enforcement of private covenants]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: enforcementMechanismAddressed Context triple: [Hurd v. Hodge, enforcementMechanismAddressed, judicial enforcement of private covenants]
-
A.
enforcementModel
chosen
Indicates the method or framework by which rules, policies, or constraints are applied, monitored, and enforced within a system or interaction.
-
B.
enforcement
Indicates the act of compelling compliance with rules, laws, or agreements through monitoring, pressure, or sanctions.
-
C.
supervisionMechanism
Indicates that one entity oversees, monitors, or regulates the actions or behavior of another through a defined control or guidance process.
-
D.
enforcementStrength
Indicates the degree or intensity with which rules, laws, or policies are applied and enforced in a given context.
-
E.
enforcedOn
Indicates that a rule, policy, or constraint is applied with authority to a particular target or subject.
- 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e2261a848190b62a8485009f8f38 |
completed | April 19, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69e4332155d88190b106d0dceb4554af |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:32 a.m.