Triple
T24849746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Laws |
E621852
|
entity |
| Predicate | repealedInPractice |
P46419
|
FINISHED |
| Object | by the late 1870s |
—
|
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: by the late 1870s | Statement: [May Laws, repealedInPractice, by the late 1870s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repealedInPractice Context triple: [May Laws, repealedInPractice, by the late 1870s]
-
A.
abolishedInPractice
chosen
Indicates that, although not formally revoked, the action or institution is no longer carried out or enforced in actual practice.
-
B.
repealed
Indicates that a law, rule, or regulation has been officially revoked or annulled so that it no longer has legal effect.
-
C.
repealedFor
Indicates that one legal rule, act, or provision has been revoked or annulled specifically in favor of, or as a consequence of, another.
-
D.
repealedUnder
Indicates that one legal rule, law, or regulation has been formally revoked or annulled by virtue of another specified legal authority or provision.
-
E.
repealedAndReenacted
Indicates that an existing law or regulation was formally revoked and simultaneously replaced by a new version covering the same subject matter.
- 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_69e2fac297e481909d3aedc75f585e42 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f43043512481909501a3979cac9947 |
completed | May 1, 2026, 4:46 a.m. |
| PD | Predicate disambiguation | batch_69f420fd375c81908ea4a4e60b76ee8f |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 5:20 a.m.