Triple
T3582297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Robinhood Markets |
E75826
|
entity |
| Predicate | RobinhoodGoldFeatures |
P49866
|
FINISHED |
| Object | margin access |
—
|
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: margin access | Statement: [Robinhood Markets, RobinhoodGoldFeatures, margin access]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: RobinhoodGoldFeatures Context triple: [Robinhood Markets, RobinhoodGoldFeatures, margin access]
-
A.
hasGoldVault
Indicates that one entity possesses or contains a vault specifically used for storing gold.
-
B.
featuresSupporter
Indicates that one entity serves as a supporter, advocate, or promoter of another entity or its cause.
-
C.
eligibleHolders
Indicates which entities are permitted or qualified to hold or possess a given item, right, or role.
-
D.
hasBlueChipStatus
Indicates that an entity holds recognized blue-chip status, signifying it is a leading, stable, and highly reputable performer within its domain.
-
E.
standardGoldContent
Indicates the specified standard or required amount of gold contained in something, typically as a measure of purity or value.
- 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_69ad85d6dc3c8190b491b79b83e25461 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc102cb2881908fa4dc1bf6fa5961 |
completed | March 8, 2026, 6:33 p.m. |
| PD | Predicate disambiguation | batch_69adb83810c481909c645c08b978edc1 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb8e4ba948190a9b777cf7f788b96 |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:21 p.m.