Triple
T24269685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P MidCap 400 Index |
E605241
|
entity |
| Predicate | componentSizeSegment |
P146598
|
FINISHED |
| Object | mid-capitalization |
—
|
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: mid-capitalization | Statement: [S&P MidCap 400 Index, componentSizeSegment, mid-capitalization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: componentSizeSegment Context triple: [S&P MidCap 400 Index, componentSizeSegment, mid-capitalization]
-
A.
divisionSize
Indicates the size or magnitude of a division or subdivided part in relation to a whole.
-
B.
sizeType
chosen
Indicates the kind or category of size associated with an entity, such as relative scale, measurement type, or size classification.
-
C.
setSize
Indicates assigning or changing the size or dimensions of an entity.
-
D.
includesSizeRange
Indicates that one entity specifies or covers a particular range of sizes associated with another entity.
-
E.
sizeDefinedBy
Indicates that the size or magnitude of one entity is determined, constrained, or specified by another entity.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d58666881909f28f4d4f0f7d590 |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c450aa508190bc9d372a5f6ee47a |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.