Triple
T1064414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BrokerCheck |
E22977
|
entity |
| Predicate | subjectOfInformation |
P7040
|
FINISHED |
| Object | brokerage firms |
—
|
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: brokerage firms | Statement: [BrokerCheck, subjectOfInformation, brokerage firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectOfInformation Context triple: [BrokerCheck, subjectOfInformation, brokerage firms]
-
A.
subjectMatter
Indicates the topic, theme, or content area that something (such as a work, document, or discussion) is about.
-
B.
subjectType
Indicates the classification or category that defines what kind of entity the subject is.
-
C.
subjectOfWork
chosen
Indicates that one entity is the main topic, focus, or theme that a particular work (such as a book, article, or artwork) is about.
-
D.
primaryTopicOf
Indicates that a given subject is the main or central topic described by another resource (such as a document, page, or record).
-
E.
subjectCanBe
Indicates that the subject has the potential or capability to assume, become, or be classified as the specified object or state.
- 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_69a493dada0481909c43649f9843ea91 |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b8f85cc08190ae03ac6c84936cc5 |
completed | March 1, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69a4b7359eb881909c868a558861cc18 |
completed | March 1, 2026, 10:01 p.m. |
Created at: March 1, 2026, 7:42 p.m.