Triple
T16705444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ORLY |
E405955
|
entity |
| Predicate | isRetailInvestorAccessible |
P92462
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [ORLY, isRetailInvestorAccessible, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRetailInvestorAccessible Context triple: [ORLY, isRetailInvestorAccessible, yes]
-
A.
isAvailableToRetailInvestors
chosen
Indicates that a financial product or offering can be legally accessed, purchased, or participated in by retail (non-professional) investors.
-
B.
investorAccess
Indicates that one party has permission or the ability to view, use, or interact with investment-related information, tools, or opportunities associated with another party or resource.
-
C.
hasPrimaryInvestor
Indicates that an entity has a main or leading investor that provides the primary financial backing or funding.
-
D.
typeOfInvestor
Indicates the kind or category of investor that a given entity is classified as.
-
E.
investorLimitTier1
Indicates the maximum allowable participation or allocation for investors classified in the first (highest-priority) limit tier.
- 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e383355f908190be467a12079b3d6f |
completed | April 18, 2026, 1:12 p.m. |
| PD | Predicate disambiguation | batch_69e319c379f88190ac0adf812486f598 |
completed | April 18, 2026, 5:42 a.m. |
Created at: April 10, 2026, 5:19 a.m.