Triple
T6715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Emergency Banking Act |
E133
|
entity |
| Predicate | fieldOfLaw |
P450
|
FINISHED |
| Object | financial law |
—
|
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: financial law | Statement: [Emergency Banking Act, fieldOfLaw, financial law]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldOfLaw Context triple: [Emergency Banking Act, fieldOfLaw, financial law]
-
A.
legalForm
Indicates the specific legal structure or organizational type under which an entity is formally constituted and recognized by law.
-
B.
legalBasis
Indicates the legal rule, authority, or justification under which an action, decision, or status is established or carried out.
-
C.
fieldOfWork
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
-
D.
subjectMatter
chosen
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
E.
judicialBody
Indicates that an entity serves as a court or tribunal with authority to adjudicate legal disputes or interpret and apply the law.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.