Triple
T23670377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell Style Indexes |
E584711
|
entity |
| Predicate | valueCriteria |
P36515
|
FINISHED |
| Object | book-to-price ratio |
—
|
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: book-to-price ratio | Statement: [Russell Style Indexes, valueCriteria, book-to-price ratio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: valueCriteria Context triple: [Russell Style Indexes, valueCriteria, book-to-price ratio]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
evaluationCriteriaInclude
chosen
Indicates that certain criteria are part of, or explicitly included in, the set of standards used to evaluate something.
-
C.
listingCriterion
Indicates the rule or standard used to determine how items are selected, ordered, or displayed in a listing.
-
D.
compositionCriterion
Indicates the rule or standard by which components are selected, combined, or arranged to form a whole.
-
E.
valueDefinedBy
Indicates that the value of one entity is determined, specified, or constrained 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_69e24901421881908c17a5293bdd4a8e |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b40ec52c8190b38a77cc3973d112 |
completed | April 29, 2026, 7:32 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:50 p.m.