Triple
T5340771
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Form BD |
E123937
|
entity |
| Predicate | requiresSignatureOf |
P63096
|
FINISHED |
| Object | authorized officer of the broker-dealer |
—
|
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: authorized officer of the broker-dealer | Statement: [Form BD, requiresSignatureOf, authorized officer of the broker-dealer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiresSignatureOf Context triple: [Form BD, requiresSignatureOf, authorized officer of the broker-dealer]
-
A.
hasSignFor
Indicates that one entity displays, bears, or provides a sign, symbol, or notice that represents, directs attention to, or gives information about another entity.
-
B.
hasSignatureRole
Indicates that an entity holds a primary, defining, or officially recognized role within a given context or relationship.
-
C.
signerOf
Indicates that an entity has signed or formally endorsed a document, agreement, or statement.
-
D.
noticeSignatoriesRequirement
Indicates that a notice must be provided to, or acknowledged by, the required signatories.
-
E.
onlyWorkSignedBy
Indicates that the referenced work is the sole work that has been signed by the specified entity.
- F. None of above. chosen
Provenance (4 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_69bd464b07f8819095aa76577c9829e4 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd85e86edc81908d87933db6489f91 |
completed | March 20, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69bd845a62b081909782863865b257a9 |
completed | March 20, 2026, 5:31 p.m. |
| PDg | Predicate description generation | batch_69bd85e69e808190b29548670fd2900a |
completed | March 20, 2026, 5:37 p.m. |
Created at: March 20, 2026, 2 p.m.