Triple
T8460085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wade–Davis Bill |
E200017
|
entity |
| Predicate | didBecomeLaw |
P49484
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Wade–Davis Bill, didBecomeLaw, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: didBecomeLaw Context triple: [Wade–Davis Bill, didBecomeLaw, no]
-
A.
signedIntoLawIn
Indicates that a proposed law or bill was formally approved and enacted by an authorized official in a specific place or jurisdiction.
-
B.
didNotBecome
chosen
Indicates that an expected or potential change of state, role, or condition between entities did not occur.
-
C.
becamePublicLaw
Indicates that a proposed law or bill has successfully completed the legislative process and has been formally enacted as public law.
-
D.
became
Indicates a change of state or status in which one entity transitions into or assumes the role, condition, or identity of another.
-
E.
introducedByLaw
Indicates that something (such as a rule, measure, or change) came into effect or was established as a result of a specific law being enacted.
- 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_69ca83198c4c8190a337bf717d1813f5 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe49fca788190a8728ff74f4d26f5 |
completed | March 31, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69cbd0fc634481909842c0a30077bfde |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:10 p.m.