Triple
T32572654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell 3000 Value Index |
E832556
|
entity |
| Predicate | styleBoxPosition |
P79746
|
FINISHED |
| Object | broad-market value |
—
|
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: broad-market value | Statement: [Russell 3000 Value Index, styleBoxPosition, broad-market value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleBoxPosition Context triple: [Russell 3000 Value Index, styleBoxPosition, broad-market value]
-
A.
stylePositioning
Indicates how an entity is spatially or visually arranged or aligned relative to a reference frame or other elements.
-
B.
styleBoxCategory
chosen
Indicates a classification relationship where a style box is assigned to a specific category or type.
-
C.
positionStyle
Indicates how an entity is positioned or arranged relative to a reference frame, layout, or context.
-
D.
structureStyle
Indicates the architectural or design style characterizing how a structure is built or formed.
-
E.
styleOrientation
Indicates the general stylistic direction or aesthetic approach that characterizes how something is designed, presented, or expressed.
- 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_69f34927bb308190ad94da1b11cad13c |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
Created at: May 1, 2026, 1:03 a.m.