Triple
T9884702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russell 3000 Index |
E180899
|
entity |
| Predicate | usesSelectionCriterion |
P64049
|
FINISHED |
| Object | U.S. domicile |
—
|
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: U.S. domicile | Statement: [Russell 3000 Index, usesSelectionCriterion, U.S. domicile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesSelectionCriterion Context triple: [Russell 3000 Index, usesSelectionCriterion, U.S. domicile]
-
A.
selectionCriteria
Indicates the conditions or rules used to choose certain entities from a larger set.
-
B.
usedToSelect
chosen
Indicates that one entity serves as a criterion, tool, or basis for choosing or determining another entity.
-
C.
hasSelectionFor
Indicates that one entity holds or specifies a chosen option, subset, or configuration on behalf of another entity.
-
D.
isSelective
Indicates that the relationship or action involves choosing or affecting only certain specific entities or options while excluding others based on particular criteria.
-
E.
hasSelectionStandard
Indicates that there is a defined criterion or set of rules used to choose or filter items, options, or entities.
- 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_69ca828082cc8190a40f8d299caa6545 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb45549488190833200977d558e47 |
completed | April 2, 2026, 12:12 a.m. |
| PD | Predicate disambiguation | batch_69cd1d810ed48190a252b70e9390c8f3 |
completed | April 1, 2026, 1:28 p.m. |
Created at: March 30, 2026, 8:38 p.m.