Triple
T31610974
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSCI USA Value Index |
E806624
|
entity |
| Predicate | coversMarketSegment |
P146868
|
FINISHED |
| Object | large-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: large-cap stocks | Statement: [MSCI USA Value Index, coversMarketSegment, large-cap stocks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversMarketSegment Context triple: [MSCI USA Value Index, coversMarketSegment, large-cap stocks]
-
A.
coversMarket
Indicates that one entity operates in, serves, or has business presence within a particular market or geographic/sectoral area.
-
B.
marketSegmentCoverage
Indicates the extent to which a product, service, or campaign reaches or serves the intended market segment(s).
-
C.
marketSegmentType
chosen
Indicates the specific category or segment of the market that an entity, product, or service is targeted toward or associated with.
-
D.
governsMarketSegment
Indicates that an entity has controlling influence or regulatory authority over a particular market segment.
-
E.
offersMarketSegment
Indicates that a provider makes a specific market segment available as a target or recipient for its products, services, or offerings.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f79f48acec8190a9d5964581a94f6c |
completed | May 3, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f79e4888248190be2f63cdfb5cd7b7 |
completed | May 3, 2026, 7:13 p.m. |
Created at: April 30, 2026, 10:36 p.m.