Triple
T4575555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial Accounting Standards Board |
E123132
|
entity |
| Predicate | usesDueProcess |
P924
|
FINISHED |
| Object | public comment on exposure drafts |
—
|
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: public comment on exposure drafts | Statement: [Financial Accounting Standards Board, usesDueProcess, public comment on exposure drafts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDueProcess Context triple: [Financial Accounting Standards Board, usesDueProcess, public comment on exposure drafts]
-
A.
endedDueTo
Indicates that an event, process, or state came to a conclusion specifically because of a particular cause or condition.
-
B.
usedProcess
chosen
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
legalProcedureUsed
Indicates that a particular legal procedure or process is applied or employed in relation to a case, action, or legal matter.
-
D.
usedDuring
Indicates that one entity is employed, applied, or active in the course of another entity’s process, event, or time period.
-
E.
usesCaseManagementSystem
Indicates that an entity makes use of a case management system to organize, track, or handle cases or workflows.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58dfe3508190b21836079e951a3c |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5228b70c8190ac48705e35a710c1 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.