Triple
T31611010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSCI USA Value Index |
E806624
|
entity |
| Predicate | hasValuationMetrics |
P66029
|
FINISHED |
| Object | price-to-book |
—
|
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: price-to-book | Statement: [MSCI USA Value Index, hasValuationMetrics, price-to-book]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasValuationMetrics Context triple: [MSCI USA Value Index, hasValuationMetrics, price-to-book]
-
A.
hasValuation
Indicates that an entity is assigned or associated with a specific assessed value or worth.
-
B.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
C.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
-
D.
hasNotableMetric
chosen
Indicates that an entity is associated with a specific metric or measurement that is considered significant or noteworthy in its context.
-
E.
instrumentValuation
Indicates the assessed monetary value assigned to a financial instrument at a given time.
- 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_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 10:36 p.m.