Triple
T9604109
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell Microcap Index |
E231926
|
entity |
| Predicate | segmentOfMarket |
P16877
|
FINISHED |
| Object | micro-cap stocks |
—
|
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: micro-cap stocks | Statement: [Russell Microcap Index, segmentOfMarket, micro-cap stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentOfMarket Context triple: [Russell Microcap Index, segmentOfMarket, micro-cap stocks]
-
A.
targetMarket
Indicates the group of consumers or organizations that a product, service, or campaign is specifically intended and designed to reach.
-
B.
marketSegmentCoverage
Indicates the extent to which a product, service, or campaign reaches or serves the intended market segment(s).
-
C.
coreMarket
Indicates that an entity serves as the primary or most important market for another entity’s products, services, or activities.
-
D.
offersMarketSegment
Indicates that a provider makes a specific market segment available as a target or recipient for its products, services, or offerings.
-
E.
brandSegment
chosen
Indicates the specific market segment or customer group that a brand is targeted toward or associated with.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a5cddf481909aa6b589bcb3e71a |
completed | April 1, 2026, 10:21 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a6fd2481908efd131e207b8143 |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:08 p.m.