Triple
T26714463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell U.S. Equity Indexes |
E673511
|
entity |
| Predicate | segmentBy |
P161155
|
FINISHED |
| Object | large-cap |
—
|
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 | Statement: [Russell U.S. Equity Indexes, segmentBy, large-cap]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: segmentBy Context triple: [Russell U.S. Equity Indexes, segmentBy, large-cap]
-
A.
segmentBy
chosen
Indicates dividing something into distinct parts or sections based on a specified criterion or boundary.
-
B.
separatesBy
Indicates that one entity divides, partitions, or creates a boundary between two or more other entities.
-
C.
partitionOf
Indicates that one entity represents a subdivision or component segment of another entity, such that together similar entities collectively form the whole.
-
D.
segmentStructure
Indicates that one entity represents a structural or organizational subdivision (a segment) within the overall structure of another entity.
-
E.
separatesAt
Indicates that one entity divides or splits another entity into distinct parts at a specific point, boundary, or location.
- 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_69eecda3a22881908f3061c760b9d542 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620debeb48190b7db395fb86cf8d9 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 27, 2026, 3:37 a.m.