Triple
T31962661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PaineWebber |
E816086
|
entity |
| Predicate | hadNumberOfFinancialAdvisors |
P173062
|
FINISHED |
| Object | over 8,000 |
—
|
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: over 8,000 | Statement: [PaineWebber, hadNumberOfFinancialAdvisors, over 8,000]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNumberOfFinancialAdvisors Context triple: [PaineWebber, hadNumberOfFinancialAdvisors, over 8,000]
-
A.
investmentAdvisor
Indicates that one entity provides professional guidance or management services to another regarding financial investments.
-
B.
approximateFolioCount
Indicates an estimated or rough number of folios associated with an entity, rather than an exact counted total.
-
C.
requiresCorporateAdviser
Indicates that one entity must have or engage a corporate adviser in relation to another entity or activity.
-
D.
hasNumberOfTradersApproximate
Indicates an approximate or estimated count of traders associated with an entity.
-
E.
estimatedNumberOfBeneficiaries
Indicates the approximate count of individuals or entities expected to receive benefits from something.
- 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_69f348f4ec708190abbb2a7c3ed58844 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b2e818e4819088fc7699503d4242 |
completed | May 3, 2026, 2:28 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
| PDg | Predicate description generation | batch_69f6b21da77081908c5c015c4606d344 |
completed | May 3, 2026, 2:25 a.m. |
Created at: May 1, 2026, 12:09 a.m.