Triple
T31581069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RUT |
E805823
|
entity |
| Predicate | commonlyComparedWith |
P278
|
FINISHED |
| Object | S&P 500 Index |
—
|
NE NERFINISHED |
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: S&P 500 Index | Statement: [RUT, commonlyComparedWith, S&P 500 Index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyComparedWith Context triple: [RUT, commonlyComparedWith, S&P 500 Index]
-
A.
sometimesComparedTo
Indicates that one entity is occasionally likened or contrasted to another, but not consistently or universally.
-
B.
comparisonUses
Indicates that one entity employs another entity as a basis or tool for making a comparison.
-
C.
isComparedTo
chosen
Indicates that one entity is evaluated or measured in relation to another to highlight similarities, differences, or relative qualities.
-
D.
comparisonUnit
Indicates that one entity serves as the reference or baseline unit against which another entity is compared or measured.
-
E.
comparisonType
Indicates the specific kind of comparison being made between two or more values or entities (e.g., equality, inequality, ordering, or similarity).
- 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_69f348d3a86c8190a3e5e539a4dd125f |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: April 30, 2026, 10:23 p.m.