Triple
T410707
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Banking Act of 1935 |
E9482
|
entity |
| Predicate | legislativeStatus |
P6734
|
FINISHED |
| Object | in force as amended |
—
|
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: in force as amended | Statement: [Banking Act of 1935, legislativeStatus, in force as amended]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: legislativeStatus Context triple: [Banking Act of 1935, legislativeStatus, in force as amended]
-
A.
legislatureStatus
Indicates the current standing, condition, or phase of a legislative body or legislative process (e.g., active, pending, dissolved, or completed).
-
B.
hasLegalStatus
Indicates that an entity possesses a particular legal classification, recognition, or standing under law.
-
C.
typeOfLegislation
Indicates the specific category or kind of legislation that a given legal act or measure belongs to.
-
D.
establishedByStatute
Indicates that something has been formally created, defined, or authorized through a specific law or statute.
-
E.
legislativeOutcome
chosen
Indicates the result or final status of a legislative process, such as whether a proposed law or measure was passed, rejected, amended, or otherwise resolved.
- 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_69a2e80111fc8190961d5b7c6154123f |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ed31681c8190ac32334562fb17fd |
completed | Feb. 28, 2026, 1:27 p.m. |
| PD | Predicate disambiguation | batch_69a2e9737694819080fde9adcc1aa4d4 |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:09 p.m.