Triple
T347300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foreign Bank and Financial Accounts Reports |
E6968
|
entity |
| Predicate | filingDeadline |
P8546
|
FINISHED |
| Object | April 15 following the calendar year reported |
—
|
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: April 15 following the calendar year reported | Statement: [Foreign Bank and Financial Accounts Reports, filingDeadline, April 15 following the calendar year reported]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: filingDeadline Context triple: [Foreign Bank and Financial Accounts Reports, filingDeadline, April 15 following the calendar year reported]
-
A.
hasDeadline
chosen
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
appealDeadlineCivil
Indicates the deadline by which an appeal must be filed in a civil case.
-
C.
dateOfSubmission
Indicates the specific date on which something (such as a document, application, or assignment) was formally submitted.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
depositionDate
Indicates the date on which something (such as a document, sample, or record) was formally submitted, filed, or placed into a repository or system.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1a37c08190b1380f6bf8513a37 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.