Triple
T5340639
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IARD |
E123934
|
entity |
| Predicate | primaryUserType |
P63093
|
FINISHED |
| Object | registered investment adviser 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: registered investment adviser firms | Statement: [IARD, primaryUserType, registered investment adviser firms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryUserType Context triple: [IARD, primaryUserType, registered investment adviser firms]
-
A.
primaryUser
Indicates that the referenced user is the main or principal user associated with a given account, resource, or context.
-
B.
primaryUsersRole
Indicates the role that a primary user holds in relation to a given resource, system, or context.
-
C.
primaryUserGroup
Indicates the main or default user group to which a user is primarily assigned or associated.
-
D.
primaryType
Indicates the main or most fundamental category or classification assigned to an entity, distinguishing it from any secondary or auxiliary types.
-
E.
primaryPatientType
Indicates the main category or classification of patient that is primarily associated with or targeted by an entity, action, or service.
- 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.