Triple
T8939905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Public Law 73-67 |
E212871
|
entity |
| Predicate | effectOfKeyCase |
P53074
|
FINISHED |
| Object | Title I declared unconstitutional |
—
|
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: Title I declared unconstitutional | Statement: [Public Law 73-67, effectOfKeyCase, Title I declared unconstitutional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOfKeyCase Context triple: [Public Law 73-67, effectOfKeyCase, Title I declared unconstitutional]
-
A.
eventEffect
chosen
Indicates the resulting change, outcome, or consequence that one event has on another state, entity, or event.
-
B.
keyAction
Indicates an action that is performed using a key, typically involving locking, unlocking, or otherwise operating a mechanism that requires a key.
-
C.
letterCase
Indicates the relationship between a character or string and its typographical case (such as uppercase, lowercase, or mixed case).
-
D.
tookEffect
Indicates that a change, rule, condition, or event became active, operative, or started producing its intended consequences.
-
E.
effectOnSpelling
Indicates a relationship where one factor influences or alters the way something is spelled.
- 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_69ca839694c88190b324ffeb43d23b08 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc66b7484481909e0d7610552f5386 |
completed | April 1, 2026, 12:28 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed5267c8190a43feb2a2f3df1ec |
completed | March 31, 2026, 11:55 p.m. |
Created at: March 30, 2026, 6:58 p.m.